Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (idunn.apache.osuosl.org: domain gmail.com designates
 66.249.82.238 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=XObTGqZ2xbheUWFtA4mMJxH18yJ1wOhQmGmBFQ6Ewlw9odQzQagIaxRzeOr91P/9ZD9ojsg5xJlID07nsrgo6m3Z8CQGOEitEUtoHqsW/UkMGZTljVEpWTfse1COARc/JZe0pWJDxsxv316GGGjl/xNcAEaH/kv7JnMQWnF2CAo=
Message-ID: <bc79dd600609140641v302ee0e0p93a2f1571ebf7e2a@mail.gmail.com>
Date: Thu, 14 Sep 2006 20:41:43 +0700
From: "Mikhail Fursov" <mike.fursov@gmail.com>
To: harmony-dev@incubator.apache.org
Subject: Re: [testing] optimization regressions (was: Re: [result] Re: [vote]
 HARMONY-1363 - DRLVM fixes and additions)
In-Reply-To: <469bff730609140146q3646583fn6bcbdf413b5c2c36@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_22706_1268890.1158241303222"
References: <906dd82e0609140105v70948c2br770994bb99591711@mail.gmail.com>
	 <469bff730609140146q3646583fn6bcbdf413b5c2c36@mail.gmail.com>

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

This would be the best solution to test if an optimization works as
expected.
We can create the following framework inside Jitrino compiler to test
individual optimizations and optimizations inter-dependencies:

Create a special optimization ("test") that that works only for "special"
Java method (jitrino.TestCase.testJitrino) during the compilation.
It works in the following way:
1) Cleans current IR
2) Set up some kind of template IR: e.g. IR with 1 loop and a const inside
the loop
3) Runs a test that uses internal Jitrino API and checks the results: e.g.
runs some loop optimizations and checks that constant is moved out from the
loop.
4) Restores initial IR of the method.

Such tests could be run from junit with a special adapter as usual Java
tests.

Does it makes sense?
Any other ideas or experience how to test compiler optimizations
predictably?


On 9/14/06, Pavel Ozhdikhin <pavel.ozhdikhin@gmail.com> wrote:
>
> *Re-sending to the new thread:*
>
>
> The right solution might also be a JIT testing framework which would
> understand the JIT IRs and check if some code patterns have been optimized
> as expected. Such way we can guarantee necessary optimizations are done
> independently of the user environment.
>
>

-- 
Mikhail Fursov

------=_Part_22706_1268890.1158241303222--