Re: [drlvm] the big soup of VM properties (HARMONY-1626)

[Mikhail Fursov <mi...@gmail.com>]

Here info about EM and JIT modules:

1) "org.apache.harmony.vm.vmdir" - EM uses this property to locate JIT
libraries.
2) "vm.use_interpreter" - EM uses this property to detect if it's
interpreter only mode.
3) "em.*" all EM properties. Actually there are only two today: a) "
em.properties" - the same as -Xem b) "em.jitPath" - to override JIT path for
all JITs in the active config
4) "jit.*" - parsed by Jitrino compiler. Strictly checked for correctness.

All of the properties above are used only during startup, before any user's
code is executed.


On 10/6/06, Geir Magnusson Jr. <ge...@pobox.com> wrote:
>
> So one of the interesting things that jumped out of me is the number of
> various library and boot classpath properties that we have floating
> around, and I'd like to
>
> 1) understand this
> 2) get rid of all the ones that we don't need
>
> Is there a defined set we need to support?  Anyone have suggestions?
>
> geir
>
>
-- 
Mikhail Fursov

Re: [drlvm] the big soup of VM properties (HARMONY-1626)

["Geir Magnusson Jr." <ge...@pobox.com>]

On Oct 9, 2006, at 8:47 AM, Mikhail Fursov wrote:

> Here info about EM and JIT modules:
>
> 1) "org.apache.harmony.vm.vmdir" - EM uses this property to locate JIT
> libraries.
> 2) "vm.use_interpreter" - EM uses this property to detect if it's
> interpreter only mode.
> 3) "em.*" all EM properties. Actually there are only two today: a) "
> em.properties" - the same as -Xem b) "em.jitPath" - to override JIT  
> path for
> all JITs in the active config
> 4) "jit.*" - parsed by Jitrino compiler. Strictly checked for  
> correctness.
>

Thanks.  I wasn't as concerned with the em* and jit* as much as the  
props used for classpath setup...

geir

> All of the properties above are used only during startup, before  
> any user's
> code is executed.
>
>
> On 10/6/06, Geir Magnusson Jr. <ge...@pobox.com> wrote:
>>
>> So one of the interesting things that jumped out of me is the  
>> number of
>> various library and boot classpath properties that we have floating
>> around, and I'd like to
>>
>> 1) understand this
>> 2) get rid of all the ones that we don't need
>>
>> Is there a defined set we need to support?  Anyone have suggestions?
>>
>> geir
>>
>>
> -- 
> Mikhail Fursov


---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org