From: Joseph Myers <joseph@codesourcery.com>
To: Daniel Kolesa <daniel@octaforge.org>
Cc: libc-alpha@sourceware.org, eery@paperfox.es,
musl@lists.openwall.com,
Will Springer <skirmisher@protonmail.com>,
Palmer Dabbelt via binutils <binutils@sourceware.org>,
via libc-dev <libc-dev@lists.llvm.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: ppc64le and 32-bit LE userland compatibility
Date: Tue, 2 Jun 2020 13:40:23 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2006021334170.24059@digraph.polyomino.org.uk> (raw)
In-Reply-To: <b44b3aa7-f9cc-43e1-b2c4-0edb6ea06189@www.fastmail.com>
On Tue, 2 Jun 2020, Daniel Kolesa wrote:
> not be limited to being just userspace under ppc64le, but should be
> runnable on a native kernel as well, which should not be limited to any
> particular baseline other than just PowerPC.
This is a fairly unusual approach to bringing up a new ABI. Since new
ABIs are more likely to be used on new systems rather than switching ABI
on an existing installation, and since it can take quite some time for all
the software support for a new ABI to become widely available in
distributions, people developing new ABIs are likely to think about what
new systems are going to be relevant in a few years' time when working out
the minimum hardware requirements for the new ABI. (The POWER8 minimum
for powerpc64le fits in with that, for example.)
> either the AIX/ELFv1 nor the ELFv2 ABIs) If we were to introduce new
> ports, what would those use? ld64.so.3 for BE/v2? ld.so.2 for LE/32-bit?
Rather than relying on numbers such as "3" or 2" in a particular place
being unique across all (architecture, ABI) pairs supported by glibc,
something more obviously specific to a particular architecture and ABI,
e.g. ld-linux-powerpc64be-elfv2.so.1, would be better.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-06-02 13:40 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 19:03 ppc64le and 32-bit LE userland compatibility Will Springer via Libc-alpha
2020-05-29 19:24 ` [musl] " Rich Felker
2020-05-30 22:56 ` Will Springer via Libc-alpha
2020-05-30 15:37 ` Christophe Leroy
2020-05-30 22:17 ` Will Springer via Libc-alpha
2020-06-05 23:54 ` Will Springer via Libc-alpha
2020-06-12 5:13 ` Christophe Leroy
2020-05-30 19:22 ` Segher Boessenkool
2020-05-31 0:57 ` Will Springer via Libc-alpha
2020-05-31 20:42 ` Segher Boessenkool
2020-05-31 22:29 ` [musl] " Daniel Kolesa
2020-06-02 1:36 ` Segher Boessenkool
2020-06-01 21:28 ` Joseph Myers
2020-06-01 21:36 ` [musl] " Rich Felker
2020-06-01 23:26 ` Daniel Kolesa
2020-06-01 23:45 ` Joseph Myers
2020-06-01 23:55 ` Joseph Myers
2020-06-02 0:13 ` Daniel Kolesa
2020-06-02 0:11 ` Daniel Kolesa
2020-06-02 13:40 ` Joseph Myers [this message]
2020-06-02 14:23 ` Michal Suchánek
2020-06-02 15:13 ` Daniel Kolesa
2020-06-02 15:27 ` Michal Suchánek
2020-06-02 15:40 ` Daniel Kolesa
2020-06-02 15:56 ` Michal Suchánek
2020-06-04 17:20 ` Segher Boessenkool
2020-06-04 17:12 ` Segher Boessenkool
2020-06-04 17:18 ` [musl] " Rich Felker
2020-06-04 17:33 ` Segher Boessenkool
2020-06-04 17:46 ` Rich Felker
2020-06-04 19:00 ` David Edelsohn via Libc-alpha
2020-06-04 19:37 ` Rich Felker
2020-06-04 20:39 ` Daniel Kolesa
2020-06-04 21:10 ` Segher Boessenkool
2020-06-04 21:43 ` Daniel Kolesa
2020-06-04 22:08 ` Joseph Myers
2020-06-04 22:26 ` Daniel Kolesa
2020-06-05 0:02 ` Segher Boessenkool
2020-06-04 23:42 ` Segher Boessenkool
2020-06-04 23:35 ` Segher Boessenkool
2020-06-05 2:18 ` Daniel Kolesa
2020-06-05 17:27 ` Segher Boessenkool
2020-06-05 17:50 ` Rich Felker
2020-06-05 23:45 ` Segher Boessenkool
2020-06-05 21:59 ` Daniel Kolesa
2020-06-06 0:12 ` Segher Boessenkool
2020-06-06 2:13 ` Daniel Kolesa
2020-06-04 21:55 ` Phil Blundell via Libc-alpha
2020-06-04 22:06 ` Daniel Kolesa
2020-06-04 23:06 ` Segher Boessenkool
2020-06-04 23:43 ` Phil Blundell via Libc-alpha
2020-06-02 14:52 ` Daniel Kolesa
2020-06-02 2:12 ` Segher Boessenkool
2020-06-02 2:17 ` Daniel Kolesa
2020-06-02 13:50 ` Joseph Myers
2020-06-02 17:47 ` Segher Boessenkool
2020-06-02 1:58 ` Segher Boessenkool
2020-06-02 2:09 ` [musl] " Jeffrey Walton via Libc-alpha
2020-06-02 2:12 ` Daniel Kolesa
2020-06-02 2:36 ` Segher Boessenkool
2020-06-02 2:55 ` Daniel Kolesa
2020-06-02 1:42 ` Segher Boessenkool
2020-06-02 2:03 ` Daniel Kolesa
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2006021334170.24059@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=daniel@octaforge.org \
--cc=eery@paperfox.es \
--cc=libc-alpha@sourceware.org \
--cc=libc-dev@lists.llvm.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=musl@lists.openwall.com \
--cc=skirmisher@protonmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).