From: Nathan Chancellor <nathan@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Tom Rini <trini@konsulko.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>, Tom Rix <trix@redhat.com>,
llvm@lists.linux.dev
Subject: Re: [PATCH] kbuild: add $(CLANG_CFLAGS) to KBUILD_CPPFLAGS
Date: Mon, 10 Apr 2023 10:25:54 -0700 [thread overview]
Message-ID: <20230410172554.GA178820@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20230409145358.2538266-1-masahiroy@kernel.org>
Hi Masahiro,
Nit: s/CLANG_CFLAGS/CLANG_FLAGS/ in the title and a small typo below.
On Sun, Apr 09, 2023 at 11:53:57PM +0900, Masahiro Yamada wrote:
> When preprocessing arch/*/kernel/vmlinux.lds.S, the target triple is
> not passed to $(CPP) because we add it only to KBUILD_{C,A}FLAGS.
>
> As a result, the linker script is preprocessed with predefined macros
> for the build host instead of the target.
>
> Assuming you use an x86 build machine, compare the following:
>
> $ clang -dM -E -x c /dev/null
> $ clang -dM -E -x c /dev/null -target aarch64-linux-gnu
>
> There is no actual problem presumably because our linker scripts do not
> rely on such predefined macros, but it is better to define correct ones.
>
> Move $(CFLAGS_CFLAGS) to KBUILD_CPPFLAGS, so that all *.c, *.S, *.lds.S
^ CLANG_FLAGS
> will be processed with the proper target triple.
>
> Reported-by: Tom Rini <trini@konsulko.com>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
We will need to sort out the report from the kbuild test robot before we
can do this. Otherwise, I think this should be fine, although I am
curious if -Wunused-command-line-argument might fire more because there
may be flags are unused while preprocessing. I will run this through my
test matrix once the other report has been addressed to make sure there
is nothing else obviously wrong with this change.
Cheers,
Nathan
> ---
>
> scripts/Makefile.clang | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/scripts/Makefile.clang b/scripts/Makefile.clang
> index 70b354fa1cb4..93ca059cc3b8 100644
> --- a/scripts/Makefile.clang
> +++ b/scripts/Makefile.clang
> @@ -38,6 +38,5 @@ CLANG_FLAGS += -Werror=unknown-warning-option
> CLANG_FLAGS += -Werror=ignored-optimization-argument
> CLANG_FLAGS += -Werror=option-ignored
> CLANG_FLAGS += -Werror=unused-command-line-argument
> -KBUILD_CFLAGS += $(CLANG_FLAGS)
> -KBUILD_AFLAGS += $(CLANG_FLAGS)
> +KBUILD_CPPFLAGS += $(CLANG_FLAGS)
> export CLANG_FLAGS
> --
> 2.37.2
>
next prev parent reply other threads:[~2023-04-10 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-09 14:53 [PATCH] kbuild: add $(CLANG_CFLAGS) to KBUILD_CPPFLAGS Masahiro Yamada
2023-04-09 20:09 ` kernel test robot
2023-04-10 17:17 ` Nathan Chancellor
2023-04-10 17:25 ` Nathan Chancellor [this message]
2023-05-31 21:33 ` Nathan Chancellor
2023-06-02 15:25 ` Nathan Chancellor
2023-06-03 16:32 ` Masahiro Yamada
2023-06-05 15:21 ` Nathan Chancellor
2023-06-06 1:29 ` Masahiro Yamada
2023-06-22 17:06 ` Fangrui Song
2023-06-23 5:40 ` Masahiro Yamada
2023-06-03 16:23 ` Masahiro Yamada
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=20230410172554.GA178820@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=trini@konsulko.com \
--cc=trix@redhat.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