From: Miko Larsson <mikoxyzzz@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Miko Larsson <mikoxyzzz@gmail.com>,
linux-kbuild@vger.kernel.org, x86@kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Nick Desaulniers <ndesaulniers@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Sean Christopherson <seanjc@google.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Chris Down <chris@chrisdown.name>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
John Ogness <john.ogness@linutronix.de>,
Elliot Berman <quic_eberman@quicinc.com>,
Oleksandr Natalenko <oleksandr@redhat.com>
Subject: [PATCH 0/2] Kconfig: -O3 enablement
Date: Tue, 21 Jun 2022 15:35:24 +0200 [thread overview]
Message-ID: <20220621133526.29662-1-mikoxyzzz@gmail.com> (raw)
Hi,
This very small series allows -O3 to be used for all architectures. The
first patch marks -O3 as experimental, with the reasoning being that it
might expose unwanted regressions to users, and the second patch
actually allows -O3 by removing the "depend on ARC" string.
The reasoning behind this series is to open up -O3 so that bugs related
to it (both compiler-related and kernel-related) can be discovered by
eyeballs wanting to improve the "-O3 experience," as that might be
beneficial to both compilers and the kernel. This has been attempted
before [1], but unfortunately nothing ever came of it.
[1] https://lore.kernel.org/lkml/20191211104619.114557-1-oleksandr@redhat.com/
Cc: linux-kbuild@vger.kernel.org
Cc: x86@kernel.org
Cc: Nathan Chancellor <nathan@kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>
Cc: Nick Desaulniers <ndesaulniers@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Sean Christopherson <seanjc@google.com>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Chris Down <chris@chrisdown.name>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: John Ogness <john.ogness@linutronix.de>
Cc: Elliot Berman <quic_eberman@quicinc.com>
Cc: Oleksandr Natalenko <oleksandr@redhat.com>
Miko Larsson (2):
Kconfig: Mark -O3 as experimental
Kconfig: Allow -O3 for all architectures
init/Kconfig | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-21 13:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 13:35 Miko Larsson [this message]
2022-06-21 13:35 ` [PATCH 1/2] Kconfig: Mark -O3 as experimental Miko Larsson
2022-06-21 13:35 ` [PATCH 2/2] Kconfig: Allow -O3 for all architectures Miko Larsson
2022-06-21 16:16 ` [PATCH 0/2] Kconfig: -O3 enablement Nick Desaulniers
2022-06-22 1:57 ` Masahiro Yamada
2022-06-23 15:42 ` Miko Larsson
2022-06-23 15:44 ` Masahiro Yamada
2022-06-23 17:00 ` Miko Larsson
2022-06-23 17:15 ` Masahiro Yamada
2022-06-23 17:44 ` Miko Larsson
2022-06-23 17:27 ` Arnd Bergmann
2022-06-24 18:29 Linus Torvalds
[not found] ` <CA+55aFyugRmHNV1BbhB_YHf3mgaiU6ND_KL8bu0PPEaRVNwWHg@mail.gmail.com>
2022-06-24 18:38 ` Linus Torvalds
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=20220621133526.29662-1-mikoxyzzz@gmail.com \
--to=mikoxyzzz@gmail.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=chris@chrisdown.name \
--cc=dmitry.torokhov@gmail.com \
--cc=gustavoars@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=oleksandr@redhat.com \
--cc=quic_eberman@quicinc.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--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
all inboxes | Powered by JetHome®