On Thursday 06 July 2006 20:29, Ciaran McCreesh wrote:
> Incidentally, syncing CFLAGS and CXXFLAGS really isn't a good idea if
> you want your C compiler to work and produce vaguely sane code.
I never said to keep them _identical_
I have a set of common flags (between which I have my arch flags) and a set of 
flags for C only and one for C++ only.

Again, it does not add more complexity than there is now to handle some 
situations.

> Not really. The __MAGIC__ is subject to change whenever any GCC person
> feels like it.
It's not magic. But if you think that going by that trick you can magically 
turn me in agreeing with you, good luck.

> It also doesn't work in cases where people have one of 
> those nasty corner case CPUs (such as the 4m, which is not an m and not
> really a 4 either, or the USIV, or the r8k) that's best off with a weird
> march.
That's what the -m{,no-}{mmx,sse,sse2,sse3,3dnow,3dnowex} flags are for.

> Well that's kinda the point. Since ebuild developers don't have access
> to every kind of CPU, relying upon the ebuilds getting it right isn't a
> very good idea.
The MMX code either works or don't. Not much to think about different CPUs.

> Since when was Gentoo about covering up for idiots who can't get their
> ricing correct at the expense of those who know what they're doing?
Again, I don't see any loss for who knows what he's doing.

> Sure it's magic. The __DEFINES__ aren't reliable. The GCC people change
> them around now and again for compatibility with other compilers.
Yeah _some_ of them are unreliable. Not those tho, as they are just the same 
on all the GCC we support. And I doubt that next week GCC 4.1.2 changes them 
around.

> Setting CFLAGS and praying is not asking for something. Setting a
> MY_X86_CPU_DOES_THIS_MKAY variable is asking for something.
And if you know what your CPU does, is it that difficult to tell the compiler 
to use them?

-- 
Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE

Attachment: pgpp6VcnIQYsT.pgp
Description: PGP signature

Reply via email to