Thanks, that helps a lot.
On 4/18/07, Pavel Ozhdikhin <[EMAIL PROTECTED]> wrote:
On 4/19/07, Nathan Beyer <[EMAIL PROTECTED]> wrote:
>
> On 4/18/07, Rana Dasgupta <[EMAIL PROTECTED]> wrote:
> > On 4/18/07, Nathan Beyer <[EMAIL PROTECTED]> wrote:
> > >
> > > No, no no! We need to be able to run on a non-SSE2 CPU without special
> > > command-line properties.
> > >
> >
> > That is what I heard Mikhail say...add a p5 pass to every jit
> > configuration ( default off ) and switch it on automatically only if
> > the jit detects a non SSE2 cpu. No additional command line properties
> > needed.
> >
>
> Then what does this mean?
>
> > 2) a. After the commit: Make it turned off by default and use
> > additional cmd-line -XX:jit.arg.codegen.p5=on when run on PC without
> SSE2
>
> Did I read that wrong?
>
> I feel like you guys are speaking in a different language here. Maybe
> I'm just behind on a few things, but I got lost in all of the EM, OPT,
> JET, conf, k5, p5 references. Is there lexicon reference somewhere, so
> I can match this stuff up to the DRLVM documentation on the web site?
> Is the web site the most up-to-date reference for this [1]?
>
> -Nathan
>
> [1] http://harmony.apache.org/subcomponents/drlvm/
>
Nathan,
The doc reference you mentioned will give you most of the details. I'll try
to interpret some of the terms:
EM - Execution Manager, the component which chooses right JIT configuration
at VM startup
OPT - Jitrino.OPT optimizing JIT compiler
JET - Jitrino.JET baseline JIT compiler
conf - config file for JIT configurations. There are several such config
files in bin/default directory. EM chooses one at VM startup.
client.emconfis the default,
server.emconf is agressive optimizing config for server apps, jet.emconf -
uses Jitrino.JET only, opt.emconf - uses Jitrino.OPT only.
p5 - optimization pass for Jitrino.OPT JIT compiler which substitutes SSE
instructions with non-SSE (introduced in HARMONY-3246)
k5 - I think Mikhail meant p5 here. :)
thanks,
Pavel
