From: Miko Larsson <mikoxyzzz@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, Nathan Chancellor <nathan@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
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: Re: [PATCH 0/2] Kconfig: -O3 enablement
Date: Thu, 23 Jun 2022 19:00:47 +0200 [thread overview]
Message-ID: <2650588.mvXUDI8C0e@sakura.myxoz.lan> (raw)
In-Reply-To: <CAK7LNAQqJc74MGFyU6fvhM9VkDKYUXyCt0NF1qAr1RmfUqC0=w@mail.gmail.com>
On Thursday, 23 June 2022 17:44:57 CEST Masahiro Yamada wrote:
> On Fri, Jun 24, 2022 at 12:42 AM Miko Larsson <mikoxyzzz@gmail.com> wrote:
> > On Wednesday, 22 June 2022 03:57:34 CEST Masahiro Yamada wrote:
> > > If you want to say "use this option carefully",
> > > EXPERT might be another option.
> > >
> > > depends on ARC || EXPERT
> >
> > Yeah, this would be a fair compromise, though I think it would be
> > better to use "visible if" instead of "depends on". I can get a v2 of
> > the series together if this is desired.
>
> Why is "visible if" better than "depends on"?
>
Technically it most likely doesn't matter, but logically it makes more
sense, since we'd make CC_OPTIMIZE_FOR_PERFORMANCE_O3 be visible if
we're on ARC or if we have EXPERT enabled, instead of depending on
them. But yeah, it probably doesn't matter.
--
~miko
next prev parent reply other threads:[~2022-06-23 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 13:35 [PATCH 0/2] Kconfig: -O3 enablement Miko Larsson
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 [this message]
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=2650588.mvXUDI8C0e@sakura.myxoz.lan \
--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=masahiroy@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;
as well as URLs for NNTP newsgroup(s).