From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: GCC 4.6.0
Date: Sun, 3 Apr 2011 04:19:23 -0600 [thread overview]
Message-ID: <20110403041923.51ea816d@gentoo.org> (raw)
In-Reply-To: pan.2011.04.03.05.50.32@cox.net
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Sun, 3 Apr 2011 05:50:32 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:
> 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?
I doubt we will. If a package breaks because of -Ofast there's really
nothing we can do about it. It's not a bug in the compiler or the package,
it's that you explicitly told it to generate non-standard-conformant code.
--
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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-04-03 10:14 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 ` [gentoo-dev] " Duncan
2011-04-03 10:19 ` Ryan Hill [this message]
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=20110403041923.51ea816d@gentoo.org \
--to=dirtyepic@gentoo.org \
--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