Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <427B7D73.5060505@www.mprojects.wiu.edu>
Date: Fri, 06 May 2005 09:21:39 -0500
From: scott hutinger <srh@www.mprojects.Horrabin.wiu.edu>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [j2me] jit sources etc
References: <427B0295.5040407@www.mprojects.wiu.edu>
 <427B7574.5080407@debrunners.com>
In-Reply-To: <427B7574.5080407@debrunners.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

To get a device up and running, it's nice to have the jit source (part 
of the jvm) to get stats and various information about the compiled 
sources.  On devices with different type of resources, it's nice to know 
as much as one can about the runtime classes.  In this case, derby would 
be the runtime classes.

So getting the sources for the jit would allow a multitude of 
information to be gathered that one normally could not do.

scott

Daniel John Debrunner wrote:

>scott hutinger wrote:
>  
>
>>I initiated looking for the jit sources.  No feedback as of this current
>>time; and my thoughts are this is a needed thing.
>>Possibly some other persons need to look into this needed item.
>>    
>>
>
>What is the jit source?
>
>Derby relies on a java virtual machine in order to function. The JIT is
>part of the JVM, not part of Derby. For any embedded device use, e.g.
>J2ME, the assumption is that the device provides a J2ME/CDC/Foundation
>virtual machine.
>
>Dan.
>
>  
>