Re: [Sablevm-user] hello

[Etienne G. <gag...@uq...>]

Vladimir Levin wrote:
> I am looking at using Java for embedded development. I am wondering if 
> SableVM is suitable for embedded development? How does it compare to GCJ?

SableVM's runtime memory footprint can be pretty low, I guess.  You can setup
the initial heap size to 0 byte, and the increment to 1 byte, so that SableVM
will tend to have as small a heap as possible (somewhat).

Also, you can compile it with -Os, to optimize size.  [Many of the m4 macros
in place to add robustness can be easily modified to expand to even smaller code.]

At runtime, the bytecode gets very little expansion (for preparation), compared
to compiled code (gross figure; some times it's the other way around for specific
bytecode sequences).

SableVM is a "traditional" kind of JVM; it does no ahead of time compiling,
not runtime compilation.  It can result in smaller code.  But, it will not
compete in speed with highly optimized code, or adaptive optimization systems
such as JikesRVM.

Etienne

-- 
Etienne M. Gagnon, Ph.D.             http://www.info.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/