On Sun, 12 Dec 2010 13:09:08 -0500
ross smith <r...@umich.edu> wrote:

> Perhaps  something along the lines of: If CPU_FLAGS is empty or not defined,
> set flags based on the -march and -mtune variables.  If CPU_FLAGS is set,
> respect what has been set there and ignore the other logic for defaults.

-march flags are the lowest common denominator for an architecture.  For
example, core2 enables MMX, SSE, SSE2, SSE3, and SSSE3 while a Core i7
processor also supports SSE4.1, SSE4.2, and AES instructions.  It might be
useful to use -march as a base and leave it up to the user to set any
additional flags, but I don't see how that is any different than what we have
now.

In addition it would require us to maintain accurate mappings of what -march
enables what flags and deal with the fact that these flags may not exist
between gcc versions.  It also falls apart with -march=native.

-- 
fonts, gcc-porting,                  it makes no sense how it makes no sense
toolchain, wxwidgets                           but i'll take it free anytime
@ gentoo.org                EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

Attachment: signature.asc
Description: PGP signature

Reply via email to