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


On Tue, Oct 19, 2004 at 05:00:40PM -0400, Andrew Pinski wrote:
> 
> On Oct 19, 2004, at 4:58 PM, Eric Botcazou wrote:
> 
> >I thought -mtune=i486 would work on x86-64, but the answer is:
> >smod-1.c:1: error: CPU you selected does not support x86-64 
> >instruction set
> >
> >Fixed thusly.
> >
> >
> >2004-10-19 ?Eric Botcazou ?<ebotcazou@libertysurf.fr>
> >
> >	* gcc.dg/smod-1.c: Pass -mtune=i486 only on x86.
> 
> 
> You could also do -m32 -mtune=i486 for x86_64 like the other testcases
> do.

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


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