From: Marcus Meissner <mm@ns.caldera.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Compiling 2.2.19 with -O3 flag
Date: Fri, 24 May 2002 18:45:37 +0200 [thread overview]
Message-ID: <200205241645.g4OGjbE30934@ns.caldera.de> (raw)
In-Reply-To: <1022253543.962.236.camel@sinai>
In article <1022253543.962.236.camel@sinai> you wrote:
> On Fri, 2002-05-24 at 07:42, Alan Cox wrote:
>> Bench it and see. From my own experience -O3 made the kernel a lot larger
>> and reduced overall performance - in part because the kernel already
>> explicitly figures out what it wants inlined.
>>
>> Interestingly enough -Os outperformed -O2
> Heh, now that is interesting.
Not really, -Os implies -O2, cf gcc/toplev.c:
if ((p[0] == 's') && (p[1] == 0))
{
optimize_size = 1;
/* Optimizing for size forces optimize to be 2. */
optimize = 2;
}
CIao, Marcus
next prev parent reply other threads:[~2002-05-24 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 6:51 Compiling 2.2.19 with -O3 flag samson swanson
2002-05-24 14:42 ` Alan Cox
2002-05-24 15:19 ` Robert Love
2002-05-24 15:44 ` Alan Cox
2002-05-24 16:45 ` Marcus Meissner [this message]
2002-05-24 16:54 ` Robert Love
2002-05-24 17:44 ` Christoph Hellwig
2002-05-24 17:55 ` Robert Love
2002-05-24 18:00 ` Christoph Hellwig
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=200205241645.g4OGjbE30934@ns.caldera.de \
--to=mm@ns.caldera.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;
as well as URLs for NNTP newsgroup(s).