On 22.09.2009 18:05, Loïc Minier wrote:
> 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).
hmm, however, some stacktrace tests seem to be broken, but not with -O2.
Native configuration is arm-unknown-linux-gnueabi
=== libjava tests ===
Running target unix
FAIL: natevents.cc compilation
FAIL: natgetallthreads.cc compilation
FAIL: natgeterrorname.cc compilation
FAIL: natgetmethodname.cc compilation
FAIL: StackTrace2 execution - source compiled test
FAIL: StackTrace2 -findirect-dispatch execution - source compiled test
FAIL: StackTrace2 -O3 execution - source compiled test
FAIL: StackTrace2 -O3 -findirect-dispatch execution - source compiled test
FAIL: Throw_2 execution - source compiled test
FAIL: Throw_2 -findirect-dispatch execution - source compiled test
FAIL: Throw_2 -O3 execution - source compiled test
FAIL: Throw_2 -O3 -findirect-dispatch execution - source compiled test
FAIL: Throw_3 execution - source compiled test
FAIL: Throw_3 -findirect-dispatch execution - source compiled test
FAIL: Throw_3 -O3 execution - source compiled test
FAIL: Throw_3 -O3 -findirect-dispatch execution - source compiled test
FAIL: stacktrace execution - source compiled test
FAIL: stacktrace -findirect-dispatch execution - source compiled test
FAIL: stacktrace -O3 execution - source compiled test
FAIL: stacktrace -O3 -findirect-dispatch execution - source compiled test
=== libjava Summary for unix ===
# of expected passes 2530
# of unexpected failures 20
# of untested testcases 16
On 22.09.2009 18:05, Loïc Minier wrote: gcc.gnu. org/bugzilla/ show_bug. cgi?id= 21285 as a test case for
> 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://
> 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).
hmm, however, some stacktrace tests seem to be broken, but not with -O2.
Native configuration is arm-unknown- linux-gnueabi
=== libjava tests ===
Running target unix
FAIL: natevents.cc compilation
FAIL: natgetallthreads.cc compilation
FAIL: natgeterrorname.cc compilation
FAIL: natgetmethodname.cc compilation
FAIL: StackTrace2 execution - source compiled test
FAIL: StackTrace2 -findirect-dispatch execution - source compiled test
FAIL: StackTrace2 -O3 execution - source compiled test
FAIL: StackTrace2 -O3 -findirect-dispatch execution - source compiled test
FAIL: Throw_2 execution - source compiled test
FAIL: Throw_2 -findirect-dispatch execution - source compiled test
FAIL: Throw_2 -O3 execution - source compiled test
FAIL: Throw_2 -O3 -findirect-dispatch execution - source compiled test
FAIL: Throw_3 execution - source compiled test
FAIL: Throw_3 -findirect-dispatch execution - source compiled test
FAIL: Throw_3 -O3 execution - source compiled test
FAIL: Throw_3 -O3 -findirect-dispatch execution - source compiled test
FAIL: stacktrace execution - source compiled test
FAIL: stacktrace -findirect-dispatch execution - source compiled test
FAIL: stacktrace -O3 execution - source compiled test
FAIL: stacktrace -O3 -findirect-dispatch execution - source compiled test
=== libjava Summary for unix ===
# of expected passes 2530
# of unexpected failures 20
# of untested testcases 16