[Mono-list] x86 JIT

[James Kevin Scott]

In message <000001c10a36$4d665b70$1699b48c@cp102230a>, "John Zedlewski" writes:
>> There is one big technical drawback with using gcc that I didn't
>mention
>> in my earlier message, namely that accurate GC is going to be a
>problem,
>> so you may have to stick with conservative GC.
>
>I don't see why this should be a problem just because no current gcc
>language uses precise GC. Whenever an object is instantiated, you can
>just have gcc emit a quick, inline call to a GC runtime function, like:
>"describe_to_gc(void* obj_addr, size_t obj_size)." The runtime GC will
>also have access to class descriptions, so it can easily look at the
>memory addresses stored in reference fields and build the whole
>reference tree however it wants to.

Maybe I'm missing something, but how does this scheme communicate to the
collector which temporaries and registers contain pointers to objects.

-K

--
Kevin Scott                          PhD Student,  Dept. of Computer Science
kscott@cs.virginia.edu                       University of Virginia       
http://www.cs.virginia.edu/~jks6b            +1 804 982 2391 (work)