From: Matt <dirtbird@ntlworld.com>
To: bunk@fs.tum.de
Cc: linux-kernel@vger.kernel.org
Subject: Re:Re: [2.6 patch] add a config option for -Os compilation
Date: Sat, 18 Oct 2003 12:50:41 +0100 [thread overview]
Message-ID: <3F912911.4080707@ntlworld.com> (raw)
> The main effect of -Os compared to -O2 (besides disabling some
> reordering of the code and prefetching) is the disabling of various
> alignments. I doubt that's a win on all CPUs.
Well the big win I found from -Os is the disabling of code inlining.
So I found I got much better code from -finline-limit=100. I
found this value after trial and error (via a bit of bench marking).
Mind you this is what works for my athlon.. Mind you the
difference isnt that huge.. I found turning on -Winline and
-finline-limit handy for finding the culprits of huge inlines..
matt
reply other threads:[~2003-10-18 11:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F912911.4080707@ntlworld.com \
--to=dirtbird@ntlworld.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome