From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: scott thomason <scott-kernel@thomasons.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel GCC Optimizations
Date: Sat, 21 Dec 2002 23:26:22 -0200 [thread overview]
Message-ID: <20021222012621.GA1212@conectiva.com.br> (raw)
In-Reply-To: <200212211920.28985.scott-kernel@thomasons.org>
Em Sat, Dec 21, 2002 at 07:20:28PM -0600, scott thomason escreveu:
> On Saturday 21 December 2002 04:10 pm, folkert@vanheusden.com wrote:
> > > > Is there any risk using -O3 instead of -O2 to compile the
> > > > kernel, and why?
> > >
> > > * It might uncover subtle bugs that would otherwise not occur.
> >
> > I wonder: for the sake of performance and good use of the precious
> > clock- cycles, shouldn't there be made a start of fixing those
> > bugs? Assuming that the bugs you're talking about are not
> > compiler-bugs, they *are* bugs in the code that should be fixed,
> > shouldn't they?
> >
> > > * Compiling with unusual options means that less people will know
> > > about any problems it causes you.
> >
> > So, let's make it -O6 per default for 2.7.x/3.1.x?
>
> Let's not. I'd rather have the best kernel developers concentrating on
> finishing important kernel features rather than digging their way out
> of esoteric optimizer debugging sessions only to find it was a flaw
> in gcc. The difference in performance boost between -O2 and greater
> levels isn't usually enough to make a significant impact, not as
> significant as the introduction of important new features, for
> example.
Sometimes even _reducing_ the optimization for performance level makes it
faster, try with -Os. And this was already discussed here and elsewhere,
reading the archives would help a lot avoiding adding more noise to the list.
- Arnaldo
next prev parent reply other threads:[~2002-12-22 1:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 17:35 Kernel GCC Optimizations Ro0tSiEgE
2002-12-21 18:08 ` axel
2002-12-21 22:13 ` folkert
2002-12-21 18:11 ` John Bradford
2002-12-21 22:10 ` folkert
2002-12-21 22:44 ` John Bradford
2002-12-22 7:57 ` Zack Weinberg
2002-12-22 1:20 ` scott thomason
2002-12-22 1:26 ` Arnaldo Carvalho de Melo [this message]
2002-12-22 1:26 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2002-12-22 13:23 Joao Seabra
2002-12-25 6:16 ` Adam Majer
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=20021222012621.GA1212@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=scott-kernel@thomasons.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