From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from brightrain.aerifal.cx (brightrain.aerifal.cx [216.12.86.13]) by sourceware.org (Postfix) with ESMTPS id 8875038708F0 for ; Thu, 4 Jun 2020 17:18:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8875038708F0 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=libc.org Authentication-Results: sourceware.org; spf=none smtp.mailfrom=dalias@libc.org 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 Subject: Re: [musl] Re: ppc64le and 32-bit LE userland compatibility 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) X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, SPF_HELO_NONE, SPF_NONE, TVD_SUBJ_NUM_OBFU_MINFP, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 17:18:46 -0000 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