This is the mail archive of the gcc-patches@gcc.gnu.org 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: 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
 > x86_64-*-*.
 > 
 > 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.
 > 
 > Janis

I've had similar problems on sparc*, see: 
gcc.c-torture/execute/20020227-1.x
gcc.c-torture/execute/simd-5.x

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
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu


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