From: Krzysztof Kozlowski <krzk@kernel.org>
To: Oleksandr Natalenko <oleksandr@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jessica Yu <jeyu@kernel.org>, Tejun Heo <tj@kernel.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
David Howells <dhowells@redhat.com>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Dan Williams <dan.j.williams@intel.com>,
"Eric W . Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH RFC] init/Kconfig: enable -O3 for all arches
Date: Tue, 10 Dec 2019 16:37:09 +0100 [thread overview]
Message-ID: <CAJKOXPfN4r+fi5R0GOyvQnQ6yn7hQvi+cScDD5THqF8X0nOX7w@mail.gmail.com> (raw)
In-Reply-To: <20191210145657.105808-1-oleksandr@redhat.com>
On Tue, 10 Dec 2019 at 15:57, Oleksandr Natalenko <oleksandr@redhat.com> wrote:
>
> Building a kernel with -O3 may help in hunting bugs like [1] and thus
> using this switch should not be restricted to one specific arch only.
>
> Thus lets expose it. If for some reasone we have to hide it, lets hide
> it under EXPERT.
You are not hiding it under EXPERT so no need to document in commit
log theoretical future decisions.
> The commit is made against next-20191210 tag.
This does not belong to commit message. You can put such under the ---
separator.
Best regards,
Krzysztof
>
> [1] https://lore.kernel.org/lkml/673b885183fb64f1cbb3ed2387524077@natalenko.name/
>
> Signed-off-by: Oleksandr Natalenko <oleksandr@redhat.com>
> ---
> init/Kconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index a34064a031a5..b41b18edb10e 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -1228,7 +1228,6 @@ config CC_OPTIMIZE_FOR_PERFORMANCE
>
> config CC_OPTIMIZE_FOR_PERFORMANCE_O3
> bool "Optimize more for performance (-O3)"
> - depends on ARC
> imply CC_DISABLE_WARN_MAYBE_UNINITIALIZED # avoid false positives
> help
> Choosing this option will pass "-O3" to your compiler to optimize
> --
> 2.24.0
>
prev parent reply other threads:[~2019-12-10 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 14:56 [PATCH RFC] init/Kconfig: enable -O3 for all arches Oleksandr Natalenko
2019-12-10 15:37 ` Krzysztof Kozlowski [this message]
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=CAJKOXPfN4r+fi5R0GOyvQnQ6yn7hQvi+cScDD5THqF8X0nOX7w@mail.gmail.com \
--to=krzk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeyu@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=oleksandr@redhat.com \
--cc=patrick.bellasi@arm.com \
--cc=tj@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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).