This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Bug target/14960] -maltivec affects vector return with-mabi=no-altivec
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Hartmut Penner <HPENNER at de dot ibm dot com>
- Cc: Alan Modra <amodra at bigpond dot net dot au>, Aldy Hernandez <aldyh at redhat dot com>, gcc-patches at gcc dot gnu dot org, Janis Johnson <janis187 at us dot ibm dot com>
- Date: Mon, 19 Apr 2004 08:59:43 -0700
- Subject: Re: [Bug target/14960] -maltivec affects vector return with-mabi=no-altivec
- References: <OF18711F0E.08437833-ONC1256E7B.0052071C-C1256E7B.005250E1@de.ibm.com>
Hartmut Penner <HPENNER@de.ibm.com> writes:
> Alan Modra wrote:
>> I've been playing in this area today, and found you need to test
>> _both_ TARGET_ALTIVEC and TARGET_ALTIVEC_ABI. Otherwise, I had
>> testsuite failures, first one being gcc.c-torture/compile/930623-1.c
>
>> Have you run a full regression test?
>
> I did now a regression run for ppc64 and did not get the regression you
> mentioned (did not get any). But I think you are right, we should check
> for both. I will do a full bootstrap and regtest with a patch checking
> both.
Does it ever make sense for TARGET_ALTIVEC_ABI to be true when
TARGET_ALTIVEC is false? If not, why not force the former off when
the latter is not set? Then code need only check the one.
zw