Re: libjava issues with arm-linux-gcj from arm-linux-gcc 3.3.2

[Nathan M <ngmlinux at gmail dot com>]

> The GCC distribution contains everything you need.  You don't need to
> get anything from classpath.

Good.

> I would caution that it is possible that gcj/libgcj will not run very
> well on your platform.  The non-existence of libjava/sysdeps/arm
> indicates to me that not very much hacking has been done to make
> arm-linux run very well.

Is this issue resolved in 3.4.x and 4.0.1?  Or is this issue
independent of the gcc/gcj version?

> If the state of the mips port in 3.3.x is any indication it might work,
> but many things that work on x86 were non-functional.  I can see that
> ffi closures are still not implemented, so many things in
> java.lang.reflect will not work.
>
> Many bugs in the java runtime have been fixed since 3.3.x, so as long as
> you are building your own gcj toolchain, you might want to think about
> using 3.4.4 or 4.0.1 instead.

Ok, so you're suggesting that apps. compiled with arm-linux-gcj may
suffer in terms of performance as well as the possibility that they
won't work properly at all.  You mention several issues above, are you
suggesting using 3.4.x or 4.0.1 would avert these?  If so, should I
expect those newer toolchains to work properly with my arm-linux
headers (which are most likely ancient in comparison)?  As long as I
compile apps. statically with gcj, I assume there wouldn't be any
dependency conflicts with my target either?  If you don't think those
are issues, I minus well use the latest compiler (4.0.1), right?

Thanks.

-Nathan