From: "tip-bot2 for John Millikin" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: John Millikin <john@john-millikin.com>,
Nathan Chancellor <nathan@kernel.org>,
Borislav Petkov <bp@suse.de>, Ard Biesheuvel <ardb@kernel.org>,
Sedat Dilek <sedat.dilek@gmail.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/build] x86/build: Propagate $(CLANG_FLAGS) to $(REALMODE_FLAGS)
Date: Fri, 26 Mar 2021 13:13:30 -0000 [thread overview]
Message-ID: <161676441085.398.3201409589926303297.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20210326000435.4785-2-nathan@kernel.org>
The following commit has been merged into the x86/build branch of tip:
Commit-ID: 8abe7fc26ad8f28bfdf78adbed56acd1fa93f82d
Gitweb: https://git.kernel.org/tip/8abe7fc26ad8f28bfdf78adbed56acd1fa93f82d
Author: John Millikin <john@john-millikin.com>
AuthorDate: Thu, 25 Mar 2021 17:04:33 -07:00
Committer: Borislav Petkov <bp@suse.de>
CommitterDate: Fri, 26 Mar 2021 11:32:47 +01:00
x86/build: Propagate $(CLANG_FLAGS) to $(REALMODE_FLAGS)
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)' 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>
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Borislav Petkov <bp@suse.de>
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Tested-by: Sedat Dilek <sedat.dilek@gmail.com>
Link: https://lkml.kernel.org/r/20210326000435.4785-2-nathan@kernel.org
---
arch/x86/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
index 2d6d5a2..9a73e0c 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
next prev parent reply other threads:[~2021-03-26 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 0:04 [PATCH 0/3] Fix cross compiling x86 with clang Nathan Chancellor
2021-03-26 0:04 ` [PATCH 1/3] x86: Propagate $(CLANG_FLAGS) to $(REALMODE_FLAGS) Nathan Chancellor
2021-03-26 8:42 ` Sedat Dilek
2021-03-26 13:13 ` tip-bot2 for John Millikin [this message]
2021-03-26 13:38 ` John Millikin
2021-03-26 0:04 ` [PATCH 2/3] x86/boot: Add $(CLANG_FLAGS) to compressed KBUILD_CFLAGS Nathan Chancellor
2021-03-26 13:13 ` [tip: x86/build] " tip-bot2 for Nathan Chancellor
2021-03-26 0:04 ` [PATCH 3/3] efi/libstub: Add $(CLANG_FLAGS) to x86 flags Nathan Chancellor
2021-03-26 13:13 ` [tip: x86/build] " tip-bot2 for Nathan Chancellor
2021-03-26 8:43 ` [PATCH 0/3] Fix cross compiling x86 with clang Ard Biesheuvel
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=161676441085.398.3201409589926303297.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=ardb@kernel.org \
--cc=bp@suse.de \
--cc=john@john-millikin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=sedat.dilek@gmail.com \
--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®