From: Arnd Bergmann <arnd@arndb.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Oleksandr Natalenko <oleksandr@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Kconfig: default to CC_OPTIMIZE_FOR_PERFORMANCE_O3 for gcc >= 10
Date: Fri, 8 May 2020 15:04:25 +0200 [thread overview]
Message-ID: <CAK8P3a06DmZr4cJt=v+1uT4sT-E3yWkeg-YioyjK3GZR5Twunw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9p7Hri-vHfwR9GY1gPo91jVx4-hTqsZVRHiioUENRHibA@mail.gmail.com>
On Fri, May 8, 2020 at 2:07 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> On Fri, May 8, 2020 at 5:56 AM Arnd Bergmann <arnd@arndb.de> wrote:
>
> The other significant thing -- and what prompted this patchset -- is
> it looks like gcc 10 has lowered the inlining degree for -O2, and put
> gcc 9's inlining parameters from -O2 into gcc-10's -O3.
I suspect it is more complicated than that, as there are a number of
parameters that determine inlining decisions. It's also not clear whether
the ones for -O3 are generally better than the ones with -O2, or if it's
just that whatever changed caused a few surprises but is otherwise
preferable.
Did you see regressions in specific modules, or just a general slowdown
or growth in object size as the result?
Arnd
next prev parent reply other threads:[~2020-05-08 13:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 22:45 [PATCH] Kconfig: default to CC_OPTIMIZE_FOR_PERFORMANCE_O3 for gcc >= 10 Jason A. Donenfeld
2020-05-08 8:35 ` Peter Zijlstra
2020-05-08 9:02 ` Oleksandr Natalenko
2020-05-08 11:21 ` Jason A. Donenfeld
2020-05-08 11:33 ` Oleksandr Natalenko
2020-05-08 11:49 ` Arnd Bergmann
2020-05-08 12:07 ` Jason A. Donenfeld
2020-05-08 13:04 ` Arnd Bergmann [this message]
2020-05-08 15:06 ` Joe Perches
2020-05-08 15:09 ` Arnd Bergmann
2020-05-10 12:47 ` David Laight
2020-05-10 17:45 ` Joe Perches
2020-05-10 18:58 ` David Laight
2020-05-12 1:10 ` Masahiro Yamada
2020-05-11 21:57 ` [PATCH v2] " Jason A. Donenfeld
2020-05-12 0:04 ` Linus Torvalds
2020-05-12 0:09 ` Linus Torvalds
2020-05-12 0:43 ` Jason A. Donenfeld
2020-05-12 8:44 ` Richard Biener
2020-05-13 11:27 ` [PATCH] " Artem S. Tashkinov
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='CAK8P3a06DmZr4cJt=v+1uT4sT-E3yWkeg-YioyjK3GZR5Twunw@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@redhat.com \
--cc=x86@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).