From: Lionel Bouton <lionel-dev@bouton.name>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] CFLAGS paragraph for the GWN
Date: Sun, 01 Oct 2006 00:42:34 +0200 [thread overview]
Message-ID: <451EF2DA.1010301@bouton.name> (raw)
In-Reply-To: <200609301748.08239.vapier@gentoo.org>
Mike Frysinger wrote the following on 30.09.2006 23:48 :
> [...]
> `man gcc` always seemed fine to me
>
> in fact, lets read the -ffast-math section:
> -ffast-math
> This option should never be turned on by any -O option since it can
> result in incorrect output for programs which depend on an exact
> implementation of IEEE or ISO rules/specifications for math func-
> tions.
>
> this flag is never safe to use in CFLAGS
>
>
Indeed, I'll add a reminder to adventurous users to check `man gcc` (I
believe I added fast-math following an example somewhere on the web
instead of checking the man page).
>> link='http://gentoo-wiki.com/CFLAGS_matrix'
>>
>
> no way will our documentation link to gentoo-wiki.com
>
>
The GWN paragraph is mainly a 'heads-up' kind of thing, no more. Don't
confuse the GuideXML extract with an official documentation extract, GWN
uses GuideXML too :-)
>> If possible, I'd like to expand the list of 3.4.6 -> 4.1.1 upgrade
>> problems which are linked to experimental CFLAGS
>>
>
> i find maintaining a list of "safe" CFLAGS on a per-gcc basis to be a waste of
> time ... but that's just me
>
That's not the idea. The main idea is to remind people that playing with
CFLAGS is allowed, as long as you remember to revert to safe CFLAGS
before reporting bugs.
As I wasted one dev time by forgetting to check my CFLAGS, I merely
thought that maybe this wasn't a common reflex for other users too
(fast-math was the only unsafe flag I used, I'm pretty conservative and
simply was mistaken because roughly 2 years ago I didn't check the
proper source of information: the man page). Maybe very few bug reports
are caused by inadequate CFLAGS. If my problem is an uncommon exception
I won't press the matter further, there would be no point to do so.
I'll wait and see if other devs are aware of common CFLAGS gotchas
plaguing bugzilla.
Lionel.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-30 22:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 20:35 [gentoo-dev] [RFC] CFLAGS paragraph for the GWN Lionel Bouton
2006-09-30 20:58 ` Dominique Michel
2006-09-30 21:48 ` Mike Frysinger
2006-09-30 22:42 ` Lionel Bouton [this message]
2006-09-30 23:27 ` [gentoo-dev] " Ryan Hill
2006-09-30 21:48 ` Ryan Hill
2006-09-30 21:52 ` Robin H. Johnson
2006-09-30 22:37 ` Ryan Hill
2006-10-01 0:38 ` Robin H. Johnson
2006-10-01 11:23 ` Duncan
2006-10-01 16:49 ` Donnie Berkholz
2006-10-01 17:02 ` Diego 'Flameeyes' Pettenò
2006-10-01 18:00 ` Ryan Hill
2006-10-02 10:40 ` Duncan
2006-10-01 21:01 ` Jeroen Roovers
2006-10-01 0:37 ` [gentoo-dev] " George Prowse
-- strict thread matches above, loose matches on Subject: below --
2006-10-03 0:56 Lionel Bouton
2006-10-03 11:55 ` Chris Gianelloni
2006-10-03 12:26 ` Ciaran McCreesh
2006-10-03 13:15 ` Mike Frysinger
2006-10-04 8:35 ` Jan Kundrát
2006-10-03 22:37 ` Lionel Bouton
2006-10-04 12:25 ` Paul de Vrieze
2006-10-03 16:11 ` Josh Saddler
2006-10-03 17:16 ` Lionel Bouton
2006-10-03 17:22 ` Daniel Ostrow
2006-10-03 17:47 ` Charlie
2006-10-03 17:56 ` Stephen P. Becker
2006-10-03 17:49 ` Lionel Bouton
2006-10-03 20:46 ` Chris Gianelloni
2006-10-03 22:14 ` Lionel Bouton
2006-10-03 18:08 ` Simon Stelling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=451EF2DA.1010301@bouton.name \
--to=lionel-dev@bouton.name \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox