This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: AltiVec test failures
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>, Aldy Hernandez <aldyh at redhat dot com>, David Edelsohn <dje at watson dot ibm dot com>
- Date: Fri, 25 Mar 2005 09:06:30 -0500
- Subject: Re: AltiVec test failures
- References: <4243B792.3090300@codesourcery.com>
On Mar 25, 2005, at 2:02 AM, Mark Mitchell wrote:
Aldy, David --
We have a bunch of tests (like gcc.dg/altivec-14.c) that are
compilation tests for AltiVec. These tests use:
/* { dg-options "-maltivec" } */
However, if your target defaults to a processor that does not have
Altivec (like, for example, PPC 603), then the PowerPC back end
ignores -maltivec.
I would like to change these tests to do:
/* { dg-options "-maltivec -mcpu=7400" } */
so that the tests work even for these configurations.
Any objection to that change?
I thought this was fixed by:
2005-03-03 Alan Modra <amodra@bigpond.net.au>
PR target/20277
* config/rs6000/rs6000.c (rs6000_override_options): Don't allow
-mcpu to override any other explicitly given flags.
Which was applied to 3.4/4.0 branches and the mainline.
-- Pinski