Re: Binary size of statically linked java application

[David Daney <ddaney at avtrex dot com>]

Joel Dice wrote:
> Hi, Michael and Marco.
>
> On Tue, 28 Nov 2006, Lehner, Michael wrote:
>
> > > Lehner, Michael wrote:
> > >
> > > > [Lehner, Michael]
> > > > Thank you for all the interesting information you provided to me. In
> >
> > the
> >
> > > > moment I am trying to build a toolchain with ulibgcj, but I am not
> >
> > sure
> >
> > > > if this will work, because they write on the project page, that it
> >
> > is
> >
> > > > for i686/amd64/.. but I am using a mips64 in the moment and this
> >
> > type is
> >
> > > > not listed.
>
>
> I don't have a mips machine available to test with, so I can't verify it 
> myself, but it shouldn't be difficult to make micro-libgcj work on that 
> platform, assuming it already works with the standard libgcj.  Please 
> let me know if you need help.

Mips-linux is fully supported on the O32 ABI.  The 64 bit ABIs are 
lacking FFI closure support and MD_FALLBACK_FRAME_STATE_FOR, locks.h may 
need adjustment as well.

Libgcj-3.4.3 is running embedded on mipsel-linux on several hundred 
thousand HD television sets.  If you are interested in the patches we 
did to trim down libgcj for that, let me know.  The basic technique is 
to statically link and then look at the linker map to see if there are 
things included that you think should be unneeded.  If so, modify the 
libgcj source so that they are no longer referenced.

David Daney