From: Nathan Chancellor <nathan@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Koakuma <koachan@protonmail.com>,
Andreas Larsson <andreas@gaisler.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
glaubitz@physik.fu-berlin.de, Nicolas Schier <nicolas@fjasle.eu>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 0/2] sparc/build: Rework CFLAGS for clang compatibility
Date: Wed, 23 Oct 2024 09:35:52 -0700 [thread overview]
Message-ID: <20241023163552.GA4081497@thelio-3990X> (raw)
In-Reply-To: <CAK7LNARSHhKr=4jrAFUrnVwU6Yw3reybku3CEVxDnSKqBptRVQ@mail.gmail.com>
On Wed, Oct 23, 2024 at 12:29:26PM +0900, Masahiro Yamada wrote:
> With running this command in Ubuntu 24.10, I got improvements,
> but I still got another build error. (unknown argument: '-mv8plus')
> clang: error: unknown argument: '-mv8plus'
> make[5]: *** [scripts/Makefile.build:229:
> masahiro@3606c94ac88c:~/workspace/linux-kbuild$ clang --version
> Ubuntu clang version 19.1.1 (1ubuntu1)
> Is this version too old, or am I missing something?
Yes, that is the issue resolved by the pull request that Koakuma
mentioned in the changelog:
https://github.com/llvm/llvm-project/pull/98713
https://github.com/llvm/llvm-project/commit/6c270a8b9f1e1b80a6016aafb438db7dd89bcb99
which depends on some codegen changes too:
https://github.com/llvm/llvm-project/commit/aca971d336d9c7650120fc0fd6dfe58866408216
Those patches missed the LLVM 19 branch point by a couple of weeks:
https://github.com/llvm/llvm-project/commit/8f701b5df0adb3a2960d78ca2ad9cf53f39ba2fe
They are relatively simple, so maybe we would have a chance of
convincing the stable maintainer of LLVM to take them for a later 19.1
release but given how little usage this is likely to see until the full
LLVM stack is further developed, I am not sure that petition would be
worth it.
Cheers,
Nathan
next prev parent reply other threads:[~2024-10-23 16:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 16:10 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 ` [PATCH v2 2/2] sparc/build: Add SPARC target flags for compiling with clang Koakuma via B4 Relay
2024-08-02 22:42 ` 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 [this message]
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=20241023163552.GA4081497@thelio-3990X \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.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=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
all inboxes | Powered by JetHome®