Hi Nahi,

As for the IR-based work, looks good to me.  Components that will be
part of the new compiler are already in place.  There is a framework
to run different analyses and optimization passes (eliminate
unnecessary frame loads stores, live variable analyses, dead code
elimination) as well as initial work on inlining methods (but,
decisions of what to inline will still have to be made by the
interpreter / JIT compiler combination).  Lot more still needs to
happen, but I would say that the new compiler is also under dev :)

Subbu.

On Wed, Aug 25, 2010 at 12:39 AM, Nick Sieger <[email protected]> wrote:
> On Aug 24, 2010, at 22:21 , Hiroshi Nakamura wrote:
>
>> Hi,
>>
>> II'm preparing for my presentation at JRubyKaigi2010 which will be
>> held on this weekend.
>> http://jrubyconf.com/jrubykaigi2010/schedule.html.en#6
>>
>> I've not yet created final slides but can I ask you comments to my
>> materials?  I don't want to let attendees confuse by my
>> misunderstanding or wrong explanation...
>>
>> 1. JRuby JIT Compier in a nutshell
>>   http://bit.ly/JRubyJITCompilerInANutshell
>>
>> 2. JRuby Source Code Reading Guide
>>   http://bit.ly/JRubySrcReadingGuide
>>
>> 3. Ruby Interpreters and Compilers
>>   http://bit.ly/RubyInterpreters
>>
>> I have just 20 minutes for my presentation so I cannot speak all of this. :-)
>
> These all look good to me. Though I would hope Charlie can give you a final 
> word on all this -- the compiler and "fast" optz are all his doing.
>
> /Nick
>
>>
>> Regards,
>> // NaHi
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to