From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: odd endianness toolchains for crosstool
Date: Thu, 29 Aug 2024 17:51:51 +0200 [thread overview]
Message-ID: <ZtCZF_yaHnECJyZ1@zx2c4.com> (raw)
In-Reply-To: <YmX7z+BirkA3VAfW@zx2c4.com>
Hey Arnd,
On Mon, Apr 25, 2022 at 03:39:27AM +0200, Jason A. Donenfeld wrote:
> Hey Arnd,
>
> I'm again experimenting with switching to your crosstool toolchains for
> WireGuard's CI. I've hit a few snags in the process:
>
> - For powerpc, gcc needs to be built with `--enable-secureplt
> --with-long-double-64` in order for musl to run.
> - Need powerpc64le compiler (-mabi=elfv2).
> - Need mipsel compiler.
> - Need aarch64_be compiler.
> - Need armeb compiler.
> - Need mips64el compiler.
>
> While the existing compilers can all produce code for the wrong endian,
> they hit trouble when trying to link against libgcc. So generally a
> separate full toolchain is supplied for the less common endians.
>
> I have had success with arm, arm64, mips, x86_64, i386, m68k. If you're
> up for adding the above compilers to the collection, I'd be able to
> complete the transition, and then look into adding a few more
> architectures.
>
> Jason
I decided to give it another look, seeing if I could replace my musl.cc
compilers with your crosstool ones.
The actual changes required weren't so bad:
https://git.zx2c4.com/wireguard-linux/commit/?h=update-toolchain
But there's not universal success:
x86_64 - good
i386 - good
arm - good
armeb - MISSING
aarch64 - good
aarch64_be - MISSING
mips - BROKEN (doesn't like -EB)
mipsel - MISSING
mips64 - BROKEN (doesn't like -EB)
mips64el - MISSING
powerpc64 - BROKEN (wrong powerpc ABI)
powerpc64le - MISSING
powerpc - BROKEN (builds but some binaries segfault)
m68k - good
riscv64 - good
riscv32 - good
s390 - BROKEN (should be called "s390x" instead)
um - kinda broken (but not crosstool's problem)
To try these, I've been running:
ARCH=aarch64 make -C tools/testing/selftests/wireguard/qemu -j$(nproc)
or similar, against this tree:
$ git clone -b update-toolchain https://git.zx2c4.com/wireguard-linux/
So it looks like it's not quite there, but not bad either. Just FYI in
case you're interested.
Jason
next prev parent reply other threads:[~2024-08-29 15:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 1:39 odd endianness toolchains for crosstool Jason A. Donenfeld
2022-04-25 8:46 ` Arnd Bergmann
2022-04-25 11:43 ` Jason A. Donenfeld
2022-04-25 14:55 ` Arnd Bergmann
2022-04-25 15:20 ` Jason A. Donenfeld
2022-04-25 15:39 ` Arnd Bergmann
2022-04-25 15:53 ` Jason A. Donenfeld
2022-04-25 16:15 ` Arnd Bergmann
2022-04-25 17:01 ` Jason A. Donenfeld
2022-04-25 17:20 ` Jason A. Donenfeld
2022-04-25 17:40 ` Arnd Bergmann
2022-04-25 17:42 ` Jason A. Donenfeld
2022-04-28 6:43 ` Rob Landley
2024-08-29 15:51 ` Jason A. Donenfeld [this message]
2024-08-29 20:25 ` Arnd Bergmann
2024-09-03 1:23 ` Nathan Chancellor
2024-09-03 6:59 ` Arnd Bergmann
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=ZtCZF_yaHnECJyZ1@zx2c4.com \
--to=jason@zx2c4.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@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