Re: [Sablevm-developer] boot.library.path vs. boot.class.path

[Chris P. <chr...@ma...>]

Archie Cobbs wrote:

> Chris Pickett wrote:
> 
>>--property=sablevm.boot.class.path=/some-transformed-path/
>>
>>and
>>
>>--property=sablevm.boot.library.path=/some-transformed-path/
>>
>>do, or at least tell me where to look?  In other words, what is the 
>>difference between them?
> 
> 
> A class path is a search path for Java class files, while a library
> path is a search path for shared library files (e.g., ELF files), such
> as may be needed by classes that rely on external native code.


Thanks.  I was having a problem where the number of Java method calls 
was going up slightly when I specified sablevm.boot.library.path as a 
property.  I later discovered from sablevm.verbose.methods=true output 
that this is because it is a System property set in Java, and requires 
some Java calls.

So, to anybody out there running benchmarks, if you need a consistent 
number of calls / instructions across experiments and you are varying VM 
properties across experiments, the solution is to specify always the 
properties you are varying, even if for a particular experiment the 
value is equivalent to the default value.

Cheers,
Chris