This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: A Far Less Ambitous AltiVec patch
- From: Geoff Keating <geoffk at geoffk dot org>
- To: Aldy Hernandez <aldyh at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, mark at codesourcery dot com, jason at redhat dot com
- Date: 02 Feb 2004 15:26:45 -0800
- Subject: Re: A Far Less Ambitous AltiVec patch
- References: <CE878995-456D-11D8-B7FE-000393673036@apple.com><m3vfmpfael.fsf@frogsleap.quesejoda.com>
Aldy Hernandez <aldyh@redhat.com> writes:
> > + /* The "-faltivec" option should have been called "-maltivec" all along. */
> > + #define SUBTARGET_OPTION_TRANSLATE_TABLE \
> > + { "-faltivec", "-maltivec -include altivec.h" }, \
> > + { "-fno-altivec", "-mno-altivec" }, \
>
> Do we really need another option (even if just for Darwin)? This is
> just plain sick. Can't you make -maltivec include altivec.h just for
> darwin?
No. -maltivec is not the "everything you might possibly want that's
related to altivec" flag. It very specifically means "generate code
for a CPU with altivec instructions". It should not change ABI or the
language that is compiled, only code generation.
--
- Geoffrey Keating <geoffk@geoffk.org>