From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 12802 invoked from network); 4 Jun 2020 17:18:59 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 4 Jun 2020 17:18:59 -0000 Received: (qmail 17986 invoked by uid 550); 4 Jun 2020 17:18:57 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 17964 invoked from network); 4 Jun 2020 17:18:56 -0000 Date: Thu, 4 Jun 2020 13:18:44 -0400 From: Rich Felker To: Segher Boessenkool Cc: Daniel Kolesa , Michal =?utf-8?B?U3VjaMOhbmVr?= , Joseph Myers , libc-alpha@sourceware.org, eery@paperfox.es, musl@lists.openwall.com, Will Springer , Palmer Dabbelt via binutils , via libc-dev , linuxppc-dev@lists.ozlabs.org Message-ID: <20200604171844.GO1079@brightrain.aerifal.cx> References: <2047231.C4sosBPzcN@sheen> <20200602142337.GS25173@kitsune.suse.cz> <3aeb6dfe-ae23-42f9-ac23-16be6b54a850@www.fastmail.com> <20200604171232.GG31009@gate.crashing.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200604171232.GG31009@gate.crashing.org> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] Re: ppc64le and 32-bit LE userland compatibility On Thu, Jun 04, 2020 at 12:12:32PM -0500, Segher Boessenkool wrote: > On Tue, Jun 02, 2020 at 05:13:25PM +0200, Daniel Kolesa wrote: > > well, ppc64le already cannot be run on those, as far as I know (I > > don't think it's possible to build ppc64le userland without VSX in > > any configuration) > > VSX is required by the ELFv2 ABI: > > """ > Specifically, to use this ABI and ABI-compliant programs, OpenPOWER- > compliant processors must implement the following categories: This is not actually ABI but IBM policy laundered into an ABI document, which musl does not honor. Rich