From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: linux4.19/5.1/5.2: build with ELFv2 ABI on ppc64 big endian
Date: Sat, 13 Jul 2019 09:19:24 +0200 [thread overview]
Message-ID: <20190713071924.QK0-0ETa7yZ7cb6a3_umWGv3CZRxRwnZ9WZ4bUArDf0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13064@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
There's a merged pull request on the void-packages repository
linux4.19/5.1/5.2: build with ELFv2 ABI on ppc64 big endian
https://github.com/void-linux/void-packages/pull/13064
Description: This adds patches to build the kernel as ELFv2 binaries for big endian ppc64, just like is default for little endian. While IBM does not officially support this and the upstream is not interested in it (because of the former), it has some mainly performance benefits (on unrelated note, we build all big endian userland as ELFv2 also, which IBM does not support either, but musl requires it and glibc at least allows it).
I tested this on a Power Mac G5 as well as in a virtual machine and it seems to be working very nicely. It's also a small patch that shouldn't conflict with anything much ever and is trivlal to redo or even ditch if needed (userland ABI does not affect kernel ABI or the other way around), it also fixes the GCC 9.1 build by side effect (as `-mcall-aixdesc` is no longer necessary).
@pullmoll / @stenstorp, mind giving this a spin also? I think it's worth a try at least. From my side there's still some stuff to confirm, so consider WIP for now, though I'm not expecting any changes to be necessary.
next prev parent reply other threads:[~2019-07-13 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 17:48 [PR PATCH] " voidlinux-github
2019-07-13 3:01 ` voidlinux-github
2019-07-13 4:05 ` voidlinux-github
2019-07-13 4:29 ` voidlinux-github
2019-07-13 7:19 ` voidlinux-github [this message]
2019-07-13 13:27 ` voidlinux-github
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=20190713071924.QK0-0ETa7yZ7cb6a3_umWGv3CZRxRwnZ9WZ4bUArDf0@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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).