public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: GCC 4.6.0
Date: Sun, 3 Apr 2011 05:50:32 +0000 (UTC)	[thread overview]
Message-ID: <pan.2011.04.03.05.50.32@cox.net> (raw)
In-Reply-To: 20110402221112.2101b4c1@gentoo.org

Ryan Hill posted on Sat, 02 Apr 2011 22:11:12 -0600 as excerpted:

>   You may also want to test your packages with the new -Ofast option to
>   be sure it doesn't have any hardcoded assumptions about -O flags.

The release description I've read for -Ofast says it includes -fast-math, 
among other things, a flag Gentoo has always strongly discouraged (you 
break with it, you keep the pieces) and which can get bugs resolved/
invalid as a result.

Now that gcc 4.6 itself is more strongly supporting it as enabled with one 
of the -O options, is that policy going to change, or is Gentoo going to 
officially not support -Ofast, as well?

Or is that yet to be established, thru testing?

FWIW, I've always stayed away from that flag, but if Gentoo's going to 
support it now, that may well change, tho I'd certainly disable it for 
specific packages using /etc/portage/env/*, as I already do for 
-combine, in my default CFLAGS but not CXXFLAGS, for instance.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  reply	other threads:[~2011-04-03  5:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03  4:11 [gentoo-dev] GCC 4.6.0 Ryan Hill
2011-04-03  5:50 ` Duncan [this message]
2011-04-03 10:19   ` [gentoo-dev] " Ryan Hill
2011-04-03 14:04     ` Mike Frysinger
2011-04-03 16:31       ` Branko Badrljica
2011-04-03 17:29         ` Chí-Thanh Christopher Nguyễn
2011-04-03 14:56 ` [gentoo-dev] " Andreas K. Huettel
2011-04-03 17:31   ` Mike Frysinger
2011-04-06  1:37 ` [gentoo-dev] " Diego Elio Pettenò

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=pan.2011.04.03.05.50.32@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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