public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: odd endianness toolchains for crosstool
Date: Mon, 25 Apr 2022 03:39:27 +0200	[thread overview]
Message-ID: <YmX7z+BirkA3VAfW@zx2c4.com> (raw)

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


             reply	other threads:[~2022-04-25  1:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25  1:39 Jason A. Donenfeld [this message]
2022-04-25  8:46 ` odd endianness toolchains for crosstool 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
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=YmX7z+BirkA3VAfW@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