porting libgcj to PalmOS

[Alexandre Petit-Bianco]

Peter Mortier writes:

> 2) EGCS based toolchain, with binutils binutils 2.9.1, gdb4.18,
> gcc2.95.2 and the latest patches from John Marshall, to build a
> cross-compiler for PalmOS. Patches and builds fine, except for java
> support, build chokes, again no gcj :(

I guess I'll have to give it a try (I never tried the egcs patches,
since they weren't stable at the time I was looking for a PlamOS
toolchain. I'm still using prc 0.5.0) How does the build choke? I'm
guessing that by `no gcj' you mean the gcj build failed...

> 1) getting gcj to work as a front-end for my gcc-Palm-cross-compiler.

Unless gcj crashes compiling Java sources... Let us know.

> 2) building a suitable libgcj for the PalmOS: I've already started
> modifying some of the config files of the libgcj, trying to figure
> out how libgcj works and builds (there is not a lot documentation,
> you know)

You'll have to ask details to the libgcj maintainers on how libgcj
relies on C++ global ctor/dtor. I know there was problems with the C++
front-end in the past. They should be taken care of with egcs patches,
I think.

As far as porting libgcj to PalmOS, I'm just worried about the
footprint of the resulting library (or libraries, since each library
has a 32K limit.)

Otherwise, other questions (after having read
http://www.io.com/~jsproat/geocities.old/GNU_Pilot_SDK.txt ) for the
libgcj hackers are:

  - Does libgcj allocate more than 32K at a time?
  - Does libgcj deliberately uses stack frames bigger than 5K?

./A