harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Pervov" <pmcfi...@gmail.com>
Subject Re: [drlvm] “java.compiler” property
Date Mon, 16 Oct 2006 17:02:13 GMT

EM, as I see it, is interchangeable component. Should we require defining "
java.compiler" for interpreted mode from all EMs?
My idea is to initialize "java.compiler" to some default value ("none"?) in
VM, and then overwrite it with actual value wherever actual information is
available (in EM in our case).

And one question follows: what if we have three different JITs defined in EM
configuration file? :) What value "java.compiler" will contain in this case?

On 10/16/06, Mikhail Fursov <mike.fursov@gmail.com> wrote:
> On 10/16/06, Alexei Zakharov <alexei.zakharov@gmail.com> wrote:
> >
> > Moreover, the spec obliges us to do so. The real question is: is it RI
> > bug or bug in spec? Personally I am for returning non-null values in
> > all cases.
> I agree. Just tell me and I will commit the patch for EM(interpreter) and
> JIT modes.
> BTW I think that we should create interpreter.emconf file and place all VM
> properties needed for interpreter into this file.
> So, in future, when we need to add more interpreter-mode option, we will
> not
> affect the EM C++ code.
> --
> Mikhail Fursov

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message