From: Arnd Bergmann <arnd@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Arnd Bergmann <arnd@arndb.de>, Peter Smith <Peter.Smith@arm.com>
Subject: Re: [PATCH] arm64: Make CPU_BIG_ENDIAN depend on !LD_IS_LLD
Date: Tue, 2 Feb 2021 21:43:31 +0100 [thread overview]
Message-ID: <CAK8P3a19W2ejs8mtHrf6Nd6BVG8u5fM4BZB+neVEWdOmGCbLbw@mail.gmail.com> (raw)
In-Reply-To: <20210202195133.GA1481999@localhost>
On Tue, Feb 2, 2021 at 8:51 PM Nathan Chancellor <nathan@kernel.org> wrote:
> On Tue, Feb 02, 2021 at 09:04:34AM +0100, Arnd Bergmann wrote:
> > On Tue, Feb 2, 2021 at 3:25 AM Nathan Chancellor <nathan@kernel.org> wrote:
> > >
> > > Similar to commit 28187dc8ebd9 ("ARM: 9025/1: Kconfig: CPU_BIG_ENDIAN
> > > depends on !LD_IS_LLD"), ld.lld does not support aarch64 big endian,
> > > leading to the following build error when CONFIG_CPU_BIG_ENDIAN is
> > > selected:
> > >
> > > ld.lld: error: unknown emulation: aarch64linuxb
> >
> > While this is the original error message I reported, I think it would be
> > better to explain that lld actually does support linking big-endian
> > kernels but they don't boot, for unknown reasons.
>
> That statement seems to contradict what Peter Smith says:
>
> https://github.com/ClangBuiltLinux/linux/issues/1288#issuecomment-770693582
>
> https://reviews.llvm.org/D58655#1410282
Right, adding Peter to Cc for clarification. Peter, what I can tell from
experiments is that lld behaves just you describe it should, and (aside from
the command like flag handling) like ld.bfd, so I'm not sure if there are
any known deficiencies or just minor bugs when dealing with the kernel.
FWIW, I have now built a big-endian musl C library and a helloworld
binary, which I linked with ld.lld and successfully tested using
qemu-aarch64_be-static
Arnd
> > I can send a patch to address the build error and mark big-endian
> > as "depends on !LD_IS_LLD || COMPILE_TEST" to reflect that
> > and help with randconfig testing.
>
> I have no strong opinion on handling this though.
next prev parent reply other threads:[~2021-02-02 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 2:24 [PATCH] arm64: Make CPU_BIG_ENDIAN depend on !LD_IS_LLD Nathan Chancellor
2021-02-02 8:04 ` Arnd Bergmann
2021-02-02 19:51 ` Nathan Chancellor
2021-02-02 20:43 ` Arnd Bergmann [this message]
2021-02-03 10:08 ` Peter Smith
2021-02-07 2:30 ` Nathan Chancellor
2021-02-09 0:57 ` [PATCH v2] arm64: Make CPU_BIG_ENDIAN depend on ld.bfd or ld.lld 13.0.0+ Nathan Chancellor
2021-02-09 1:39 ` Nick Desaulniers
2021-02-09 14:35 ` Will Deacon
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=CAK8P3a19W2ejs8mtHrf6Nd6BVG8u5fM4BZB+neVEWdOmGCbLbw@mail.gmail.com \
--to=arnd@kernel.org \
--cc=Peter.Smith@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=will@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).