Can you have dependent types , internal references and desc. unions in the CLR ?
For Windows you cant change or remove the GC so pause-less , no heap code is a challenge the runtime libs may allocate even if unused.(Application / domain classes , reflection etc). Alternatively for mono their are whole range of performance issues. CLR has no effective SIMD support so you have to rely on linking to C libs . Windows has polymorphic caches so you don't need a separate JIT. Not sure i agree with "The set of supported targets is much richer than those for CLI" on LLVM , sure there are more weird targets but those have a subset eg only 32 or 64 bit and i doubt some of the apis / intrinsics work on them creating problems to adopt. Windows requires Visual studio windows linker / headers on LLVM but that is improving ( a new one is in Beta) . LLVM has auto vectorization. LLVM is poorly documented, Ben.
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
