From: Adrian Bunk <bunk@stusta.de>
To: David Lang <david.lang@digitalinsight.com>
Cc: christos gentsis <christos_gentsis@yahoo.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: kernel optimization
Date: Fri, 22 Jul 2005 22:15:03 +0200 [thread overview]
Message-ID: <20050722201503.GN3160@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0507221250450.23492@qynat.qvtvafvgr.pbz>
On Fri, Jul 22, 2005 at 12:52:22PM -0700, David Lang wrote:
> This is a airly frequent question
>
> the short answer is 'don't try'
>
> the longer answer is that all the additional optimization options that are
> part of O3+ are considered individually and if they make sense for the
> kernel they are explicitly enabled (in some cases the optimizations need
> to be explicitly turned off for proper functionality of the kernel under
> all versions of GCC)
As far as I can see, none of the additional optimizations with -O3 is
enabled in the kernel.
> David Lang
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-07-22 20:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 18:55 kernel optimization christos gentsis
2005-07-22 19:52 ` David Lang
2005-07-22 20:15 ` Adrian Bunk [this message]
2005-07-22 20:14 ` Adrian Bunk
2005-07-22 21:11 ` christos gentsis
2005-07-23 14:34 ` Simon Strandman
2005-07-23 5:35 ` Al Boldi
2005-07-23 6:30 ` cutaway
2005-07-23 19:50 ` Alan Cox
2005-07-23 22:03 ` cutaway
[not found] <200507231849.j6NInMPO003728@laptop11.inf.utfsm.cl>
2005-07-26 5:22 ` Al Boldi
2005-07-26 9:22 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-07-27 3:53 Al Boldi
2005-07-27 4:20 ` Lee Revell
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=20050722201503.GN3160@stusta.de \
--to=bunk@stusta.de \
--cc=christos_gentsis@yahoo.co.uk \
--cc=david.lang@digitalinsight.com \
--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