From: Carter Cheng Date: 2011-10-27T17:02:52+09:00 Subject: [ruby-core:40446] Re: JIT development for MRI --90e6ba4fc28ef2581304b0433251 Content-Type: text/plain; charset=ISO-8859-1 Thanks Koichi. I may make an attempt to implement some sort of JIT for MRI- that being said it is hard to predict the performance prior to completing the code and running tests (or I am not so good an engineer that I do have a deep intuition of this). On Thu, Oct 27, 2011 at 12:14 AM, SASADA Koichi wrote: > (2011/10/27 15:28), Carter Cheng wrote: > > Thanks Koichi. How do profiling based approaches differ from trace > recording > > in this context? > > Trace based approach is completely difference, I think. And I don't > know which is suitable for Ruby. > > (I guest that on small footprint programs, trace based one is good. And > ruby is... But I don't have any more experience) > > -- > // SASADA Koichi at atdot dot net > > --90e6ba4fc28ef2581304b0433251 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Koichi. I may make an attempt to implement some sort of JIT for MRI-= that being said it is hard to predict the performance prior to completing = the code and running tests (or I am not so good an engineer that I do have = a deep intuition of this).

On Thu, Oct 27, 2011 at 12:14 AM, SASADA Koi= chi <ko1@atdot.net> wrote:

(2011/10/27 15:28), Carter Cheng wrote:
> Thanks Koichi. How do profiling based approaches differ from trace rec= ording
> in this context?

Trace based approach is completely difference, I think. =A0And I don&= #39;t
know which is suitable for Ruby.

(I guest that on small footprint programs, trace based one is good. =A0And<= br> ruby is... =A0But I don't have any more experience)

--
// SASADA Koichi at atdot dot net