Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of mike.fursov@gmail.com
 designates 64.233.162.228 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=iTGySxZb9s8HrL0ypkFPCVpBbtcpwGswjmW9mz74K34GhbluRAMYsg5eqZB9K2613AmL075Hsh1e6YE4Cd/Co0GsoYxCBCgm4gpV1ASzBqVmMS6bG8jsxoCPHao4UdViiwZFKQtWGKisi3ABK3/bUUi05Mly1XJYDXyaB2Y0PBA=
Message-ID: <bc79dd600704201202k2051fcadsbe857c788d95c268@mail.gmail.com>
Date: Sat, 21 Apr 2007 02:02:52 +0700
From: "Mikhail Fursov" <mike.fursov@gmail.com>
To: dev@harmony.apache.org
Subject: Re: Harmony+Eclipse and Scrapbook Pages
In-Reply-To: <b6cb498e0704201031g258776aegc800863954b9f8c0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_128713_29095917.1177095772828"
References: <008201c78290$6c5108e0$6401a8c0@MARVIN>
	 <b6cb498e0704200406j677e17a9y5d485f9f9ff1558d@mail.gmail.com>
	 <4628AEAC.5090705@gmail.com>
	 <b6cb498e0704200541n6cd60984q92243ae86a12917f@mail.gmail.com>
	 <b6cb498e0704200637r4aae2dc9x26019a62a29511f@mail.gmail.com>
	 <bc79dd600704200649g104dda42s3fdad194efc888c3@mail.gmail.com>
	 <b6cb498e0704200810t4147b4a9jf6273729967d79fb@mail.gmail.com>
	 <4628DA16.4030306@gmail.com>
	 <1e3228450704200930y7c409132xcaa7a6617103ca36@mail.gmail.com>
	 <b6cb498e0704201031g258776aegc800863954b9f8c0@mail.gmail.com>

------=_Part_128713_29095917.1177095772828
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Yes, JIT mode and interpreter mode are different in class resolution
strategy.

Here how it works:
With interpreter class resolution is initiated when the class is actually
needed: object of the class is created, a static field or a static
method is invoked. This is the same as SUN behaviour. (AFAIK they use
interpreter too)

With JIT we have eager resolution today: all classes referred in a method
(and all inlined methods!) are resolved during compilation time. AFAIK BEA
works  this way too. At least, I can write tests that demonstrate it. If a
method has multiple references to a class and its resolution fails JIT asks
again an again to resolve it. Moreover, if exception happened in classloader
- it can be lost.

Now I'm working on Lazy Resolution task and going to submit it to JIRA right
after JavaOne is finished (there are a lot of changes and regressions are
possible). After it's done JIT will be able to work in either eager or lazy
mode. And I hope most of the resolution related bugs will gone after it.

BTW did you tried the same scenario with BEA?


On 4/21/07, Ivan Popov <ivan.g.popov@gmail.com> wrote:
>
> Yes, in interpreter mode step works fine. I don't see second attempt
> to load class in classloader trace while step is performed.
>
> Is it possible that in JIT mode first invocation of a method of
> already loaded class may lead to compilation and attempt to load this
> class second time?
>
> Thanks.
> Ivan
>
> On 4/20/07, Eugene Ostrovsky <eugene.s.ostrovsky@gmail.com> wrote:
> > BTW everything works fine with harmony VM in interpreter mode (-Xint
> option)
> >
> > On 4/20/07, Tim Ellison <t.p.ellison@gmail.com> wrote:
> > >
> > > Ivan Popov wrote:
> > > > Thanks, Mikhail, It might be useful, but I dont know how to specify
> > > > options for VM running Scrapbook code, it is started automatically.
> > >
> > > Select the jpage page file and choose the properties option from the
> > > context menu (Alt+Enter), in there you can find a 'Scrapbook Runtime'
> > > page where you can specify the VM and options etc it will use.
> > >
> > > Tim
> > >
> > >
> >
>


-- 
Mikhail Fursov

------=_Part_128713_29095917.1177095772828--