Interop with  other stacks and runtimes is a massive advantage with
reference counting ( or non relocating GCs)  ...and i dont just mean
calling c  but far more importantly c / C++ /Java  calling bitc.

Also if you still target the CLR i asume  you will just ignore / stop the
GC and build your own minimal GC for the cycles  ( LLVM and static compile
 becomes more attractive)

re last post not LOCK CMPXCHG but obviously LOCK INCL / LOCK DECL   wrote
some locks last year  and CMPXCHG has burned too deep... the pain... ..

Ben
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev

Reply via email to