From: Nathan Chancellor <natechancellor@gmail.com>
To: John Millikin <jmillikin@gmail.com>
Cc: hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
John Millikin <john@john-millikin.com>
Subject: Re: [PATCH v2] arch/x86: Propagate $(CLANG_FLAGS) to $(REALMODE_FLAGS)
Date: Sat, 26 Dec 2020 20:31:22 -0700 [thread overview]
Message-ID: <20201227033122.GA1993664@ubuntu-m3-large-x86> (raw)
In-Reply-To: <3b793c42-8983-4502-1f9e-729cc0ebec47@gmail.com>
On Sat, Dec 26, 2020 at 05:41:25PM +0900, John Millikin wrote:
> When cross-compiling with Clang, the `$(CLANG_FLAGS)' variable
> contains additional flags needed to build C and assembly sources
> for the target platform. Normally this variable is automatically
> included in `$(KBUILD_CFLAGS)' by via the top-level Makefile.
>
> The x86 real-mode makefile builds `$(REALMODE_CFLAGS)' from a
> plain assignment and therefore drops the Clang flags. This causes
> Clang to not recognize x86-specific assembler directives:
>
> arch/x86/realmode/rm/header.S:36:1: error: unknown directive
> .type real_mode_header STT_OBJECT ; .size real_mode_header, .-real_mode_header
> ^
>
> Explicit propagation of `$(CLANG_FLAGS)' to `$(REALMODE_CFLAGS)',
> which is inherited by real-mode make rules, fixes cross-compilation
> with Clang for x86 targets.
>
> Relevant flags:
>
> * `--target' sets the target architecture when cross-compiling. This
> flag must be set for both compilation and assembly (`KBUILD_AFLAGS')
> to support architecture-specific assembler directives.
>
> * `-no-integrated-as' tells clang to assemble with GNU Assembler
> instead of its built-in LLVM assembler. This flag is set by default
> unless `LLVM_IAS=1' is set, because the LLVM assembler can't yet
> parse certain GNU extensions.
>
> Signed-off-by: John Millikin <john@john-millikin.com>
Reviewed-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
> Changes in v2:
> - Reworded the commit message to highlight that this is for
> cross-compilation.
> - Removed the `ifdef CONFIG_CC_IS_CLANG' guard.
>
> arch/x86/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/x86/Makefile b/arch/x86/Makefile
> index 7116da3980be..412b849063ec 100644
> --- a/arch/x86/Makefile
> +++ b/arch/x86/Makefile
> @@ -33,6 +33,7 @@ REALMODE_CFLAGS += -ffreestanding
> REALMODE_CFLAGS += -fno-stack-protector
> REALMODE_CFLAGS += $(call __cc-option, $(CC), $(REALMODE_CFLAGS), -Wno-address-of-packed-member)
> REALMODE_CFLAGS += $(call __cc-option, $(CC), $(REALMODE_CFLAGS), $(cc_stack_align4))
> +REALMODE_CFLAGS += $(CLANG_FLAGS)
> export REALMODE_CFLAGS
>
> # BITS is used as extension for files which are available in a 32 bit
> --
> 2.29.2
>
>
next prev parent reply other threads:[~2020-12-27 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 7:29 [PATCH] " John Millikin
2020-12-26 7:35 ` hpa
2020-12-26 7:52 ` John Millikin
2020-12-26 7:53 ` Nathan Chancellor
2020-12-26 8:41 ` [PATCH v2] " John Millikin
2020-12-27 3:31 ` Nathan Chancellor [this message]
2021-02-03 12:19 ` Borislav Petkov
2021-02-03 12:24 ` Sedat Dilek
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=20201227033122.GA1993664@ubuntu-m3-large-x86 \
--to=natechancellor@gmail.com \
--cc=bp@alien8.de \
--cc=clang-built-linux@googlegroups.com \
--cc=hpa@zytor.com \
--cc=jmillikin@gmail.com \
--cc=john@john-millikin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®