From: Thomas Cort <linuxgeek@gmail.com>
To: gentoo-alpha@lists.gentoo.org
Subject: Re: [gentoo-alpha] optimization flags
Date: Wed, 14 Dec 2005 11:17:18 -0500 [thread overview]
Message-ID: <3b09e8e90512140817i7eeabf7bxf3541f97ebba6267@mail.gmail.com> (raw)
In-Reply-To: <43A0428A.7010300@jdfiles.org>
I use the flags from the Safe_Cflags article on the wiki (
http://gentoo-wiki.com/Safe_Cflag ). So far they haven't caused me any
headaches.
CHOST="alpha-unknown-linux-gnu"
CFLAGS="-mieee -O2 -mcpu=ev56 -pipe"
CXXFLAGS="${CFLAGS}"
> What level of optimizations flags are recommended?
On all of the Gentoo systems I've set up I've used -O2. I use it over
-O3 for a number of reasons. One, I cannot tell the difference in
terms of speed between something that is compiled with -O2 vs. -O3.
Two, emerge times are longer if you use -O3. Three, sometimes using
too many optimizations screws things up. (see
http://bugs.gentoo.org/74072 ).
-Thomas
--
gentoo-alpha@gentoo.org mailing list
prev parent reply other threads:[~2005-12-14 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 16:04 [gentoo-alpha] optimization flags Jeff Sacksteder
2005-12-14 16:17 ` Thomas Cort [this message]
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=3b09e8e90512140817i7eeabf7bxf3541f97ebba6267@mail.gmail.com \
--to=linuxgeek@gmail.com \
--cc=gentoo-alpha@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