From: "Arnd Bergmann" <arnd@arndb.de>
To: "Nathan Chancellor" <nathan@kernel.org>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "Masahiro Yamada" <masahiroy@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Nicolas Schier" <nicolas@fjasle.eu>,
"Guenter Roeck" <linux@roeck-us.net>,
"Lee Jones" <lee@kernel.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
linux-kbuild@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH 1/9] Kbuild: only pass -fno-inline-functions-called-once for gcc
Date: Fri, 11 Aug 2023 16:23:17 +0200 [thread overview]
Message-ID: <9311a5ee-a859-4601-a8ef-b0f95176327e@app.fastmail.com> (raw)
In-Reply-To: <20230811141421.GA3948268@dev-arch.thelio-3990X>
On Fri, Aug 11, 2023, at 16:14, Nathan Chancellor wrote:
> On Fri, Aug 11, 2023 at 04:03:19PM +0200, Arnd Bergmann wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> clang ignores the -fno-inline-functions-called-once option, but warns
>> when building with -Wignored-optimization-argument enabled:
>>
>> clang: error: optimization flag '-fno-inline-functions-called-once' is not supported [-Werror,-Wignored-optimization-argument]
>>
>> Move it back to using cc-option for this one.
>>
>> Fixes: 7d73c3e9c514 ("Makefile: remove stale cc-option checks")
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> How can this even be hit with clang, as CONFIG_DEBUG_SECTION_MISMATCH
> was changed to depend on GCC in the same commit?
Good question, I have not noticed that part, but I'm pretty
sure I keep hitting this issue. I'll drop it from my
series to see if I can reproduce it.
Maybe what happens is that this triggers when changing from
gcc to clang in an output directory, the stake CONFIG_*
symbols are still evaluated while parsing the initial
Makefile but then cause problems.
Arnd
next prev parent reply other threads:[~2023-08-11 14:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 14:03 [PATCH 0/9] Kbuild: warning options cleanup and more warnings Arnd Bergmann
2023-08-11 14:03 ` [PATCH 1/9] Kbuild: only pass -fno-inline-functions-called-once for gcc Arnd Bergmann
2023-08-11 14:14 ` Nathan Chancellor
2023-08-11 14:23 ` Arnd Bergmann [this message]
2023-08-11 14:03 ` [PATCH 2/9] Kbuild: consolidate warning flags in scripts/Makefile.extrawarn Arnd Bergmann
2023-08-11 14:19 ` Nathan Chancellor
2023-08-11 14:26 ` Arnd Bergmann
2023-08-12 7:21 ` Masahiro Yamada
2023-08-20 1:36 ` Masahiro Yamada
2023-08-11 14:03 ` [PATCH 3/9] Kbuild: avoid duplicate warning options Arnd Bergmann
2023-08-12 9:21 ` Masahiro Yamada
2023-08-12 9:28 ` Arnd Bergmann
2023-08-20 1:38 ` Masahiro Yamada
2023-08-11 14:03 ` [PATCH 4/9] extrawarn: don't turn off -Wshift-negative-value for gcc-9 Arnd Bergmann
2023-08-12 12:04 ` Masahiro Yamada
2023-08-11 14:03 ` [PATCH 5/9] extrawarn: enable format and stringop overflow warnings in W=1 Arnd Bergmann
2023-08-12 13:10 ` Masahiro Yamada
2023-08-20 1:40 ` Masahiro Yamada
2023-08-21 18:26 ` Nick Desaulniers
2023-08-11 14:03 ` [PATCH 6/9] extrawarn: move -Wrestrict into W=1 warnings Arnd Bergmann
2023-08-12 13:20 ` Masahiro Yamada
2023-08-20 1:45 ` Masahiro Yamada
2023-08-11 14:03 ` [PATCH 7/9] extrawarn: do not disable -Wmain at W=1 level Arnd Bergmann
2023-08-11 14:03 ` [PATCH 8/9] extrawarn: enable more warnings in W=2 Arnd Bergmann
2023-08-11 14:03 ` [PATCH 9/9] [RFC] extrawarn: enable more W=1 warnings by default Arnd Bergmann
2023-08-11 16:09 ` Nathan Chancellor
2023-08-11 18:23 ` Arnd Bergmann
2023-08-14 19:52 ` Nathan Chancellor
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=9311a5ee-a859-4601-a8ef-b0f95176327e@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=sfr@canb.auug.org.au \
/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).