From: Koakuma via B4 Relay <devnull+koachan.protonmail.com@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
glaubitz@physik.fu-berlin.de,
Masahiro Yamada <masahiroy@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, linux-kbuild@vger.kernel.org,
Koakuma <koachan@protonmail.com>
Subject: [PATCH v2 2/2] sparc/build: Add SPARC target flags for compiling with clang
Date: Wed, 17 Jul 2024 23:10:16 +0700 [thread overview]
Message-ID: <20240717-sparc-cflags-v2-2-259407e6eb5f@protonmail.com> (raw)
In-Reply-To: <20240717-sparc-cflags-v2-0-259407e6eb5f@protonmail.com>
From: Koakuma <koachan@protonmail.com>
clang only supports building 64-bit kernel, so we use the
sparc64-linux-gnu target.
See also: https://lore.kernel.org/lkml/e26PTXUXEz8OYXmaeKn4Mpuejr4IOlFfFwdB5vpsluXlYiqDdlyQTYcDtdAny_o4gO4SfPeQCCN2qpyT6e0nog5EaP3xk2SeUPTrF54p1gM=@protonmail.com/T/#m068e010dcf8b99d3510a90d7532bcdb70e2e2c6b
Signed-off-by: Koakuma <koachan@protonmail.com>
---
scripts/Makefile.clang | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/Makefile.clang b/scripts/Makefile.clang
index 6c23c6af797f..2435efae67f5 100644
--- a/scripts/Makefile.clang
+++ b/scripts/Makefile.clang
@@ -10,6 +10,7 @@ CLANG_TARGET_FLAGS_mips := mipsel-linux-gnu
CLANG_TARGET_FLAGS_powerpc := powerpc64le-linux-gnu
CLANG_TARGET_FLAGS_riscv := riscv64-linux-gnu
CLANG_TARGET_FLAGS_s390 := s390x-linux-gnu
+CLANG_TARGET_FLAGS_sparc := sparc64-linux-gnu
CLANG_TARGET_FLAGS_x86 := x86_64-linux-gnu
CLANG_TARGET_FLAGS_um := $(CLANG_TARGET_FLAGS_$(SUBARCH))
CLANG_TARGET_FLAGS := $(CLANG_TARGET_FLAGS_$(SRCARCH))
--
2.45.2
next prev parent reply other threads:[~2024-07-17 16:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 16:10 [PATCH v2 0/2] sparc/build: Rework CFLAGS for clang compatibility Koakuma via B4 Relay
2024-07-17 16:10 ` [PATCH v2 1/2] sparc/build: Remove all usage of -fcall-used* flags Koakuma via B4 Relay
2024-08-02 23:04 ` Nathan Chancellor
2024-10-24 16:29 ` Andreas Larsson
2024-10-26 14:50 ` Koakuma
2024-07-17 16:10 ` Koakuma via B4 Relay [this message]
2024-08-02 22:42 ` [PATCH v2 2/2] sparc/build: Add SPARC target flags for compiling with clang Nathan Chancellor
2024-08-03 5:58 ` Masahiro Yamada
2024-10-21 20:16 ` [PATCH v2 0/2] sparc/build: Rework CFLAGS for clang compatibility Nathan Chancellor
2024-10-22 19:10 ` Masahiro Yamada
2024-10-22 20:07 ` Nathan Chancellor
2024-10-23 0:43 ` Koakuma
2024-10-23 3:38 ` Masahiro Yamada
2024-10-23 16:45 ` Nathan Chancellor
2024-10-26 14:52 ` Koakuma
2024-10-27 11:00 ` Masahiro Yamada
2024-10-27 18:34 ` Nathan Chancellor
2024-10-23 3:29 ` Masahiro Yamada
2024-10-23 16:35 ` Nathan Chancellor
2024-10-22 19:13 ` 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=20240717-sparc-cflags-v2-2-259407e6eb5f@protonmail.com \
--to=devnull+koachan.protonmail.com@kernel.org \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=justinstitt@google.com \
--cc=koachan@protonmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=sparclinux@vger.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).