Stack size

Thu Dec 6 07:31:00 GMT 2001

BTW, using GCJ/Java vs. C++ will increase memory footprint of an
embedded app by at least 100%. At least 50% of a Java/GCJ binary
is run-time metadata which is currently stored in static data structures
that must get loaded into the data segment. Until there's a better
way of loading the metadata on demand from a compressed serialized
format, the memory footprint of a Java application will be MUCH larger
than the equivalent APP in C++.
On Thursday, December 6, 2001, at 08:24 AM, Tom Tromey wrote:
>>>>>> "Steen" == Steen Jansdal <steen@jansdal.dk> writes:
>> Steen> The reason I'm asking this is that I'm trying to evaluate if 
> Linux
> Steen> on a x86 is going to be the platform for our next embedded
> Steen> device. The memory on this device are limited to 16 or 32 Mb.
> Steen> The programs for this device are going to heavy multithreaded,
> Steen> and consist of a web-server, a soap-server and several user
> Steen> programs. It is my highest wish that we can use java as our
> Steen> language. C++ is too difficult to maintain.
>> Steen> Any advices for my evaluation are much appreciated.
>> With gcj you're always free to hack the library to do whatever you
> like. You could even add a Java API to control the stack size on a
> per-thread basis.
>> Tom