Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of gcjhd-harmony-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: harmony-dev@incubator.apache.org
From: Alex Astapchuk <alex.astapchuk@gmail.com>
Subject: Re: [drlvm][jit] Moving jet to the top level of drlvm...
Date: Mon, 06 Nov 2006 17:48:46 +0600
Lines: 51
Message-ID: <ein7ev$cch$1@sea.gmane.org>
References: <e0f125db0611030431p101cf8f8nd5d57f34a30fc353@mail.gmail.com>
 <eimivi$hr2$1@sea.gmane.org> <454F0CF7.3020702@pobox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
In-Reply-To: <454F0CF7.3020702@pobox.com>
Sender: news <news@sea.gmane.org>

Geir Magnusson Jr. wrote:
> 
> 
> Alex Astapchuk wrote:
>> Pavel Pervov wrote:
>>> Hello, community,
>>>
>>> Working through DRLVM sources I (once again) looked at organization of
>>> jitrino code.
>>>
>>> Actually, there are two JITs hidden inside "jitrino": JET and OPT.
>>>
>>> As far as I may observe - these two are code-independent from each 
>>> other.
>>>
>>> JIT-guys, could you comment?
>>>
>>> If I'm right here I would vote for moving them to top level of
>>> drlvm/trunk/vm directory to clearly indicate we have two JITs in DRLVM.
>>
>> There are no two JITs, actually. We call them 'compilation paths'.
>> 'jet' here stands for 'Jitrino Express compilation paTh'.
>>
>> As Mikhail already mentioned they share significant parts like
>> logging, PMF, multi-threaded stuff, guard locks, etc.
>>
>> The difference in codebases, came from their targets - the .jet was 
>> heavily tuned for very fast compilation, resulting to that many virtual
>> interfaces used in .opt were substituted with direct calls to VM.
>>
>> Personally, I don't see any *practical* reason to separate .jet and .opt.
>>
> 
> The practical reason is to start convincing ourselves of the modularity.

Ugh. 'Modularity' is good word, I like it.
Especially taking into account that no one can measure it. Can you? :-)

Moving jet around will give nothing useful. Neither in a short-term nor 
in a longer perspective. But will take an efforts and add a mess and 
maybe code duplicate from Jitrino codebase.

Jitrino itself is modular enough - again, the JET was not intended as a 
separate JIT. It's only purpose was (and still is) to be a front-line 
for Jitrino's main engine - to speed up client apps startup.

Absolutely no reason to have it separately.

-- 
Thanks,
   Alex