This is the mail archive of the gcc@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: Altivec Linux support in GCC


>>>>> "Michel" == Michel LESPINASSE <walken at zoy dot org> writes:

  > On Mon, Apr 14, 2003 at 12:49:48PM -0500, Kumar Gala wrote:
 >> 1. What are there two options to enable the support? (-maltivec 
 >> -mabi=altivec).  If I have a Linux PPC targeted GCC why do I need to 
 >> tell it to use the abi to get altivec code generation?  This just seems 
 >> confusing to the user (I dont have to specify the abi for any other 
 >> option).

Still, only the minority of users do this.

I agree with y'all that -maltivec without -mabi=altivec is useful,
what I have argued for in the past (and again now), is having
-maltivec imply -mabi=altivec as the default.  Then, if you want the
functionality you describe, use -maltivec -mabi=no-altivec.

Previously when I brought this up, no one gave any arguments as to why
we can't have -maltivec imply an ABI change by default and then use
-mabi=no-altivec if you want the odd-ball case.

6 out of 10 emails I get wrt altivec "bugs" I answer with "have you
passed -mabi=altivec"?  Clearly, this is confusing to the average user
who just wants to use AltiVec features as advertised in the
documentation (PIM).

Aldy


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