From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to properly change CFLAGS ?
Date: Thu, 31 Aug 2006 04:15:08 -0700 [thread overview]
Message-ID: <7573e9640608310415t2cf020afr7c6bfdb752dcb728@mail.gmail.com> (raw)
In-Reply-To: <1156978378.17760.22.camel@scarlatti.leonora.org>
On 8/30/06, Vladimir G. Ivanovic <vgivanovic@comcast.net> wrote:
> On Mon, 2006-08-21 at 20:06 -0700, Richard Fish wrote:
> > -Os seems to take much less time and memory to compile than -O2 or -O3. And being a
> > ~arch user, time-to-compile is a nice thing to reduce.
>
> It is possible that one of my usual CFLAGS options (-Wall -march=k8
> -msse3 -pipe -O2 -ffast-math) overwhelms any -Os/-O2 execution time
Well it looks like I'll have to retract that statement in relation to
-Os/-O2. My current tests with -march=pentium4 -fweb -pipe
-fomit-frame-pointer for my laptop or -march=athlon64 -fweb -pipe for
my AMD box show a <5% difference in compile time between -Os and -O2.
I think there was a bigger difference in previous versions of gcc, but
I can't seem to find any notes or anything to support that belief...
Cheers,
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-31 11:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 20:51 [gentoo-user] How to properly change CFLAGS ? Stefan G. Weichinger
2006-08-21 21:01 ` Richard Fish
2006-08-21 21:19 ` Stefan G. Weichinger
2006-08-22 3:18 ` Richard Fish
2006-08-22 7:23 ` Stefan G. Weichinger
2006-08-22 15:03 ` Bo Ørsted Andresen
2006-08-22 19:58 ` Stefan G. Weichinger
2006-08-23 21:04 ` Bo Ørsted Andresen
2006-08-23 22:54 ` Richard Fish
2006-08-23 23:31 ` Bo Ørsted Andresen
2006-08-21 21:16 ` Neil Bothwick
2006-08-21 21:27 ` Stefan G. Weichinger
[not found] ` <20060822003250.3daebfb0@krikkit.digimed.co.uk>
2006-08-22 2:28 ` Collins Richey
2006-08-22 14:16 ` Bo Ørsted Andresen
2006-08-22 3:06 ` Richard Fish
2006-08-22 7:26 ` Stefan G. Weichinger
[not found] ` <1156978378.17760.22.camel@scarlatti.leonora.org>
2006-08-31 11:15 ` Richard Fish [this message]
2006-08-22 14:12 ` Alan Mckinnon
2006-08-22 16:23 ` Dale
2006-08-22 18:36 ` Adrian Frith
2006-08-22 18:54 ` Dale
2006-08-22 19:30 ` Richard Fish
2006-08-22 20:53 ` Bo Ørsted Andresen
2006-08-22 21:02 ` Richard Fish
2006-08-22 21:04 ` Richard Fish
2006-08-22 21:19 ` Bo Ørsted Andresen
2006-08-22 21:50 ` Richard Fish
2006-08-22 21:54 ` Bo Ørsted Andresen
2006-08-22 21:24 ` Stefan G. Weichinger
2006-08-23 7:43 ` Alan Mckinnon
2006-08-23 11:29 ` Bo Ørsted Andresen
2006-08-23 14:04 ` Alan Mckinnon
2006-08-23 19:40 ` Richard Fish
2006-08-23 19:45 ` Stefan G. Weichinger
2006-08-24 7:06 ` Alan Mckinnon
2006-08-22 18:40 ` Richard Fish
2006-08-23 8:07 ` Alan Mckinnon
2006-08-23 19:06 ` Richard Fish
2006-08-23 20:22 ` Michael Hennebry
2006-08-23 20:29 ` Bo Ørsted Andresen
2006-08-23 20:49 ` Stefan G. Weichinger
2006-08-23 21:48 ` Michael Hennebry
2006-08-23 21:55 ` Stefan G. Weichinger
2006-08-23 22:21 ` Bo Ørsted Andresen
2006-08-23 22:24 ` Bo Ørsted Andresen
2006-08-23 22:50 ` Richard Fish
2006-08-24 23:31 ` Michael Hennebry
2006-08-24 7:11 ` 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=7573e9640608310415t2cf020afr7c6bfdb752dcb728@mail.gmail.com \
--to=bigfish@asmallpond.org \
--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