On Tue, Sep 12, 2006 at 12:32:35AM -0400, Jack Howarth wrote:
> On Darwin PPC at -m64, we are seeing a slew of failures
> in the tmpdir-gcc.dg-struct-layout-1 tests...
>
> FAIL: tmpdir-gcc.dg-struct-layout-1/t001 c_compat_x_tst.o-c_compat_y_tst.o
> execute
> FAIL: tmpdir-gcc.dg-struct-layout-1/t003 c_compat_x_tst.o-c_compat_y_tst.o
> execute
> FAIL: tmpdir-gcc.dg-struct-layout-1/t005 c_compat_x_tst.o-c_compat_y_tst.o
> execute
> FAIL: tmpdir-gcc.dg-struct-layout-1/t006 c_compat_x_tst.o-c_compat_y_tst.o
> execute
> FAIL: tmpdir-gcc.dg-struct-layout-1/t008 c_compat_x_tst.o-c_compat_y_tst.o
> execute
> FAIL: tmpdir-gcc.dg-struct-layout-1/t016 c_compat_x_tst.o-c_compat_y_tst.o
> execute
> FAIL: tmpdir-gcc.dg-struct-layout-1/t024 c_compat_x_tst.o-c_compat_y_tst.o
> execute
> FAIL: tmpdir-gcc.dg-struct-layout-1/t026 c_compat_x_tst.o-c_compat_y_tst.o
> execute
> FAIL: tmpdir-gcc.dg-struct-layout-1/t028 c_compat_x_tst.o-c_compat_y_tst.o
> execute
>
> The binaries left in gcc/testsuite/gcc simply abort when run. Can someone
> walk me
> through the process of creating a bug report for these? I don't quite
> understand
> how I could create .i or .s files for these since the creation of all of the
> test
> binaries seems to be automated. Thanks in advance for any help.
Are you testing two compilers against each other (i.e. are you using
ALT_CC_UNDER_TEST resp. ALT_CXX_UNDER_TEST)?
In any case, you can build the generated tests with -DDBG (guess
e.g. RUNTESTFLAGS="struct-layout-1.exp --target-board unix/-DDBG"
could work) and you'll see which test line and which check failed in the
testsuite log dump.
Then you can just cut and paste that line from the generated testcase
(the test line number is the first argument of the macro on each line)
say into say struct-layout-1_test.h and can build it as any other compat.exp
testcase.
Jakub
