[LLVMdev] Dynamic (JIT) type resolution

[Chris Lattner]

On Tue, 6 Nov 2007, Nicolas Geoffray wrote:
> Not the best way to do: what if you have many field operations on many
> classes in one method? You'll interpret the function as long as all
> field operations are not resolved?

right

>> 2. jit compile code that is slower than need be (using function calls to
>> cause the lazy stuff to happen) and then replace it when the class is
>> loaded.
>>
>
> You mean replace the code at the IR level right? and then recompile the
> function. You then have the same issue than 1).

I don't see how it's the same issue.  Once you jit it, it is just machine 
code.  Updating the machine code with better code seems like a reasonable 
and obvious optimization.

-Chris

-- 
http://nondot.org/sabre/
http://llvm.org/