From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: gcc optimization levels (was: Re: [gentoo-user] mplayer compilation)
Date: Mon, 20 Nov 2006 23:42:06 -0600 [thread overview]
Message-ID: <200611202342.11071.bss03@volumehost.net> (raw)
In-Reply-To: <45621A74.2080107@ilievnet.com>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
On Monday 20 November 2006 15:13, Daniel Iliev <danny@ilievnet.com> wrote
about 'Re: [gentoo-user] mplayer compilation':
> I don't think there is such an option for gcc "-O4". AFAIK the shorthand
> optimization options are -O, -O0, -O1, -O2, -O3 and -Os"
In addition to -Os, -O will accept any non-negative integer as an argument.
Currently, anything above 3 does nothing extra. From what I understand,
there have been undocumented levels up to 6, but they have always been
considered unstable (which is why they never appeared in documentation).
The quickest way to recognize a Gentoo ricer is someone that
has -O4, -O6, -O99 or something else equally stupid in their CFLAGS. -O3
is defensible, as it is at least *supposed to be* stable; anything higher
is just stupid.
--
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-21 5:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 14:22 [gentoo-user] mplayer compilation Pawel K
2006-11-20 14:52 ` Bo Ørsted Andresen
2006-11-20 16:18 ` Hans-Werner Hilse
2006-11-20 18:21 ` Uwe Thiem
2006-11-20 21:13 ` Daniel Iliev
2006-11-21 5:42 ` Boyd Stephen Smith Jr. [this message]
2006-11-21 9:54 ` gcc optimization levels (was: Re: [gentoo-user] mplayer compilation) Hans-Werner Hilse
2006-11-20 15:38 ` [gentoo-user] mplayer compilation Alan McKinnon
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=200611202342.11071.bss03@volumehost.net \
--to=bss03@volumehost.net \
--cc=gentoo-user@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