search for: hlvms

..., or even a change to the Type > hierarchy) Can you elaborate on a changing of the type hierarchy? > --another reason to isolate GC-handling code in your compiler. I just cannot see how the GC-handling code can be isolated in such a way that the result is better than just having separate HLVMs for separate design decisions. -- Dr Jon Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/?e

...the type hierarchy? I've considered introducing a separate GCPointer type. >> --another reason to isolate GC-handling code in your compiler. > > I just cannot see how the GC-handling code can be isolated in such a > way that > the result is better than just having separate HLVMs for separate > design > decisions. I simply suggest you group functions to 'emit read barrier', 'allocate GC root', and soforth together in your compiler such that they can be easily changed or updated in one place if it proves necessary. — Gordon

On Feb 26, 2009, at 21:17, Jon Harrop wrote: > For example, the IR I am generating shares pointers read from the > heap even across function calls. That is built on the assumption > that the pointers are immutable and, therefore, that the GC is non- > moving. [...] > > If you wanted to add a copying GC to my VM you would probably > replace every lookup of the IR

On Thursday 26 February 2009 17:25:56 Chris Lattner wrote: > In my ideal world, this would be: > > 1. Subsystems [with clean interfaces] for thread management, > finalization, object model interactions, etc. > 2. Within different high-level designs (e.g. copying, mark/sweep, etc) > there can be replaceable policy components etc. > 3. A couple of actual GC implementations built

I'm a newcomer to llvm, but what you've done so far is very impressive. Llvm is a godsend to anybody who is attempting to implement their own their own language. :-) My company is considering using llvm as the backend for a small matlab-like language for scientific computation; our other option is MSIL. After reading through the documentation, I noticed that llvm seems to have one major