Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Friday 12 November 2004 00:58, Jörg Schaible wrote:
> Seesh. You're right. I was talking about CFLAGS. Now, is there a policy
> for "standard accepted safe CFLAGS" ? I know, it is my problem, if
> something really breaks. But I have really a lot of apps running with
> my (not too esoteric) settings, and if one single app fails badly (just
> core dumps) and I can track it down to a single CFLAG flag, what is the
> actual policy (if there is one)? Why is a filter for the flag just
> recected?
One thing that I use as baseline is that if "info gcc" says that it is not
safe (such as -ffast-math, -fno-rtti, -fnoexceptions and various others).
Many of these optimization options are application specific and should be
set by the upstream build scripts. In other words, filtering away to
avoid compiler bugs is something I'm willing to do, filtering away stupid
defaults is not.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@g.o
Homepage: http://www.devrieze.net
|
|
