From: Nathan Chancellor <nathan@kernel.org>
To: Koakuma <koachan@protonmail.com>
Cc: Rosen Penev <rosenp@gmail.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
sparclinux@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.com>,
Christian Brauner <brauner@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:CLANG/LLVM BUILD
SUPPORT:Keyword:\\\\b(?i:clang|llvm)\\\\b" <llvm@lists.linux.dev>
Subject: Re: [PATCH] sparc: Avoid unsupported LLD branch relocations
Date: Wed, 20 May 2026 15:31:47 -0700 [thread overview]
Message-ID: <20260520223147.GB1607511@ax162> (raw)
In-Reply-To: <ov9qx_G3-lAxKXO_ur8gXhE8J5toGs8NkZ2mtMBdwEVND6y0f9CakihiR1kVbaS_lgMVbYs3NegNpFgCRjzzb79wzfbm4_1WeVt1q5pe_f0=@protonmail.com>
On Wed, May 20, 2026 at 04:20:50PM +0000, Koakuma wrote:
> Yes, at the moment LLD only has very basic capabilities and still can't link
> the kernel, at least not without some rather invasive changes.
> (And even if you manage to land all the changes to the kernel, still there are
> many complex programs out there that's currently unlinkable by LLD that I feel
> like improving LLD would be a better use of resources, in the long term)
Agreed and that is generally what we tried to do for all other
architectures, I don't think SPARC is special here.
> As for the integrated assembler, now that PR 187534 [1] is merged it should
> be possible to build the kernel with IAS, but that commit hasn't made it into
> a release yet so I don't feel like it's the time to update the kernel's
> docs... maybe?
>
> [1]: https://github.com/llvm/llvm-project/pull/187534
Yeah, we can update the documentation when 23.1.0 is out, but I should
update our CI to test sparc64_defconfig with the integrated assembler
for clang-23+ because we test from main.
--
Cheers,
Nathan
prev parent reply other threads:[~2026-05-20 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 4:19 [PATCH] sparc: Avoid unsupported LLD branch relocations Rosen Penev
2026-05-14 5:03 ` John Paul Adrian Glaubitz
2026-05-14 5:34 ` Rosen Penev
2026-05-14 5:40 ` John Paul Adrian Glaubitz
2026-05-14 12:58 ` Nathan Chancellor
2026-05-20 16:20 ` Koakuma
2026-05-20 22:31 ` Nathan Chancellor [this message]
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=20260520223147.GB1607511@ax162 \
--to=nathan@kernel.org \
--cc=andreas@gaisler.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=justinstitt@google.com \
--cc=koachan@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=rosenp@gmail.com \
--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