This is the mail archive of the 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: A Far Less Ambitous AltiVec patch

On 2 Feb, 2004, at 15.38, Zack Weinberg wrote:

Geoff Keating <> writes:

Aldy Hernandez <> writes:

+ /* The "-faltivec" option should have been called "-maltivec" all along. */
+ { "-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.

I object in principle to any change that involves including header files behind the user's back.

How does that differ from emitting tons of builtins behind the user's back? :-)

Ziemowit Laski                 1 Infinite Loop, MS 301-2K
Mac OS X Compiler Group        Cupertino, CA USA  95014-2083
Apple Computer, Inc.           +1.408.974.6229  Fax .5477

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