This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC 3.2 Prerelease

HJ Lu writes:

> .../configure --enable-__cxa_atexit --enable-clocale=gnu --with-system-zlib --enable-shared --enable-threads=posix --enable-haifa --disable-checking

Many of those configure flags are just the default or should not matter.
Would any be expected to make a difference in terms of tests?

> 1. gcc 3.3 using libstdc++ from gcc 3.2. Additional failures:
> +FAIL: backward/ execution test
> +FAIL: gcc.c-torture/compile/20001226-1.c,  -O1  
> +FAIL: gcc.c-torture/compile/20001226-1.c,  -O3 -fomit-frame-pointer  
> Additonal pass:
> -FAIL: 22_locale/ execution test

The C failures presumably have to do with a regression in the GCC trunk
and have nothing to do with ABI issues.

Which testsuite are you using, the 3.2 one or the 3.3 one?  Or are there
no differences in the testsuite?

> 2. gcc 3.2 using libstdc++ from gcc 3.3. Additional failures:
> +FAIL: 22_locale/ execution test
> +FAIL: Thread_Interrupt output from bytecode->native test
> +FAIL: Thread_Wait_2 execution from bytecode->native test
> +FAIL: Thread_Wait -O execution from source compiled test

The latter three are Java failures, right?  That gives us only two
extra libstdc++ failures, one in each direction.  Could you (HJ) post
more information on what the failure is in

FAIL: backward/ execution test

from part 1, and

FAIL: 22_locale/ execution test

in part 2?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]