This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PowerPC SVR4 ABI compliance fix
- From: David Edelsohn <dje at watson dot ibm dot com>
- To: Aldy Hernandez <aldyh at redhat dot com>
- Cc: Zack Weinberg <zack at codesourcery dot com>, Geoff Keating <geoffk at redhat dot com>, gcc patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 21 Nov 2001 23:24:03 -0500
- Subject: Re: PowerPC SVR4 ABI compliance fix
>>>>> Aldy Hernandez writes:
Aldy> we can't put "altivec_abi" in rs6000_current_abi because altivecabi is
Aldy> just an extension to the current abi, not a different abi. the entries
Aldy> in rs6000_current_abi are mutually exclusive.
Aldy> i guess altivec_abi doesn't need to be in target_flags, it could reside
Aldy> in any other global variable, because it's just accessed with the macro
Aldy> TARGET_ALTIVEC.
Why do we need both TARGET_ALTIVEC and TARGET_ALTIVEC_ABI? Is
this a requirement of the contract Red Hat is implementing?
David