Caolan who did the initial armel EABI port of oo.o told me to check whether firefox and gij work fine; firefox works fine in our testing in karmic and he proposed using http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21285 as a test case for gij.
I built Test.java with gcj and gcj -C --main=Test and it ran in both cases and reported the stack trace at runtime (both java byte code .class with gij and a.out).
Caolan who did the initial armel EABI port of oo.o told me to check whether firefox and gij work fine; firefox works fine in our testing in karmic and he proposed using http:// gcc.gnu. org/bugzilla/ show_bug. cgi?id= 21285 as a test case for gij.
I built Test.java with gcj and gcj -C --main=Test and it ran in both cases and reported the stack trace at runtime (both java byte code .class with gij and a.out).