From: Arnd Bergmann <arnd@arndb.de>
To: Joe Perches <joe@perches.com>
Cc: Oleksandr Natalenko <oleksandr@redhat.com>,
"Jason A. Donenfeld" <Jason@zx2c4.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 17:09:14 +0200 [thread overview]
Message-ID: <CAK8P3a2KU_4FVCYt73mmpodV3Q7ipS579BDMnai-m9HgaiFYiA@mail.gmail.com> (raw)
In-Reply-To: <c774d7371a9599526090e63e85f61e69bddf4795.camel@perches.com>
On Fri, May 8, 2020 at 5:06 PM Joe Perches <joe@perches.com> wrote:
>
> On Fri, 2020-05-08 at 13:49 +0200, Arnd Bergmann wrote:
> > Personally, I'm more interested in improving compile speed of the kernel
>
> Any opinion on precompiled header support?
I have not tried it. IIRC precompiled headers usually work best for projects
that have a large header with all the global declarations that gets included
everywhere, while Linux has always tried (with different amounts of success)
to minimize the number of headers that get included per file.
Arnd
next prev parent reply other threads:[~2020-05-08 15:09 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
2020-05-08 15:06 ` Joe Perches
2020-05-08 15:09 ` Arnd Bergmann [this message]
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=CAK8P3a2KU_4FVCYt73mmpodV3Q7ipS579BDMnai-m9HgaiFYiA@mail.gmail.com \
--to=arnd@arndb.de \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--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).