[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wizZ-HoBJ24TPFawS5zHqT+HcreqfmFRf3Cw4SS0NxV+Q@mail.gmail.com>
Date: Fri, 30 Apr 2021 15:52:52 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc: Arnd Bergmann <arnd@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Jann Horn <jannh@...gle.com>,
lkml <linux-kernel@...r.kernel.org>,
arcml <linux-snps-arc@...ts.infradead.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>
Subject: Re: Heads up: gcc miscompiling initramfs zlib decompression code at -O3
On Fri, Apr 30, 2021 at 3:44 PM Vineet Gupta <Vineet.Gupta1@...opsys.com> wrote:
>
> I agree that -O2 is default, but we've had -O3 default for ARC kernel
> forever, since last decade seriously. The reason I turned it on back
> then was upside of 10% performance improvement on select LMBench numbers
> on hardware at the time which for a rookie kernel hacker was yay momemt.
> I can revisit this and see if that is still true.
It would be interesting if you can actually show 10% improvement, and
also pinpoint things in the profile.
I (long long long ago) actually used -O6 for kernel builds as a "give
me everything you have" (I don't think gcc has actually ever done
anything more than O3, but whatever).
In fact, you can find
Q: What Does gcc -O6 Do?
in some kernel FAQ's from those historical times.
We eventually gave up on it, because it just generated bigger and
slower code, and people got very tired of all the compiler bugs.
Linus
Powered by blists - more mailing lists