linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Dan <dan.carpenter@oracle.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [RFC PATCH] kbuild: Add an option to enable -O1 and speed-up compilation time
Date: Tue, 24 May 2022 16:16:39 +0200	[thread overview]
Message-ID: <CANiq72kySVvOQ7eqwe0Jzz3V0JTtrcqODHR9Ty4-sfDMdzP6XQ@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdneqUvq+Nz_zPmJmuPFfAvWQgnzrw1AJt=WqQF2hThF-A@mail.gmail.com>

On Mon, May 23, 2022 at 8:27 PM Nick Desaulniers
<ndesaulniers@google.com> wrote:
>
> As with the Rust series, I'm not a fan of this (or
> CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE_O3):
> https://lore.kernel.org/lkml/CAKwvOd=7QTUH69+ZbT7e8einvgcosTbDkyohmPaUBv6_y8RfrQ@mail.gmail.com/

I think it should be decided whether we want extra levels or not, and
apply that policy to both the C and Rust sides.

If we don't, then yeah, let's remove them in both sides and just let
users modify `CFLAGS` as needed.

If we do, then having them as config options makes sense so that they
can be kept working.

Cheers,
Miguel

  parent reply	other threads:[~2022-05-24 14:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21  9:04 [RFC PATCH] kbuild: Add an option to enable -O1 and speed-up compilation time Christophe JAILLET
2022-05-21 15:38 ` Masahiro Yamada
2022-05-23 12:34   ` Changbin Du
2022-05-23 12:50     ` Arnd Bergmann
2022-05-23 18:26 ` Nick Desaulniers
2022-05-23 20:16   ` Christophe JAILLET
2022-05-23 20:31     ` Nick Desaulniers
2022-05-24 14:16   ` Miguel Ojeda [this message]
2022-05-23 20:25 ` Miguel Ojeda
2022-05-23 20:44   ` Christophe JAILLET
2022-05-24 14:16     ` Miguel Ojeda

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=CANiq72kySVvOQ7eqwe0Jzz3V0JTtrcqODHR9Ty4-sfDMdzP6XQ@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=ndesaulniers@google.com \
    --cc=ojeda@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).