This is the mail archive of the
mailing list for the GCC project.
Re: Fix gcc.dg/smod-1.c on x86-64
> Some of us at IBM have been wondering how to handle tests for
> powerpc64-unknown-linux-gnu that either are relevant for only 32-bit
> or 64-bit code generation, or that need xfail for one but not the
> other. The problem is complicated by the fact that we normally test a
> biarch compiler by running the entire test suite with -m32 and again
> with -m64, and there's no way to known whether GCC for target
> powerpc64-*-linux* generates only 64-bit code, defaults to 64-bit
> code, or defaults to 32-bit code. I suspect that the same is true for
> It doesn't seem like a good idea to explicitly add '-m32' to a test
> that might already be run with both -m32 and -m64.
I've had similar problems on sparc*, see:
However, the fact that the powerpc64 can *default* to 32-bit code is
an annoying complication. You may want to write some sort of dg check
to determine the default output on powerpc* and cache the result,
e.g. the stuff in testsuite/lib/target-supports.exp.
Kaveh R. Ghazi firstname.lastname@example.org