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 8725 invoked from network); 4 Jun 2020 22:08:28 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 4 Jun 2020 22:08:28 -0000 Received: (qmail 1495 invoked by uid 550); 4 Jun 2020 22:08:22 -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 1477 invoked from network); 4 Jun 2020 22:08:21 -0000 IronPort-SDR: WmDAiHNjjXNltnVqd0FJGbph1VYRcD7BK5payqSCH37aDCgLaKr4lPSBju0e/n4XJKb2S2ZtyJ 7SLDsQGWgs4iU/WR4iZuo0kndTbysHKeoPWHM7qZK9U8IUZkabhiZi9nzQ0ZaJRsZ1kcxqzbOI Yl3JCKBJbUr9Z2Lmrye/ktUO7HzOSQ5Sg7vkEIDv9KYoGwcPYCroQjCJJgb9RbnVhucUbAO3nZ RpfNn3X9zk5THOMjpFVRUwYjXFQ4xJtuBXCUkni3d0b92oyHpK9OQlI55DB+OWZdZPPuxW/rK5 k6k= X-IronPort-AV: E=Sophos;i="5.73,472,1583222400"; d="scan'208";a="49597267" IronPort-SDR: 10Lvn9hMbIgp6Wmv7tGgT/Bb+RFvig0/R1k1fveX5H7Yt2roTj6zgGCC1dp89r/XljPZBd6TNV Ylfgb2UMBeVoR3WYnwLk6A5YcMdvGzOClszLxWzKYwoHZ31s2/E4yimjtKTnS8vuBk5kl4vy9K 41mPdkl1eZFrKFmSEkxp1shYieeZTiKGLjQT+TBX3Tkz2E+OQ9inB98+0gnco8Zd+0wNmY9dG5 9c4hFdi3/PO+MQK8TUxIjjpcOkxbLfry5T4klJZULKuE+xlfW9/xN+eEkrHml9nS1RolhNufrv VCo= Date: Thu, 4 Jun 2020 22:08:02 +0000 From: Joseph Myers X-X-Sender: jsm28@digraph.polyomino.org.uk To: Daniel Kolesa CC: Segher Boessenkool , , Rich Felker , =?ISO-8859-15?Q?Michal_Such=E1nek?= , , , Will Springer , Palmer Dabbelt via binutils , via libc-dev , In-Reply-To: <60fa8bd7-2439-4403-a0eb-166a2fb49a4b@www.fastmail.com> Message-ID: References: <20200602142337.GS25173@kitsune.suse.cz> <3aeb6dfe-ae23-42f9-ac23-16be6b54a850@www.fastmail.com> <20200604171232.GG31009@gate.crashing.org> <20200604171844.GO1079@brightrain.aerifal.cx> <20200604173312.GI31009@gate.crashing.org> <20200604211009.GK31009@gate.crashing.org> <60fa8bd7-2439-4403-a0eb-166a2fb49a4b@www.fastmail.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Originating-IP: [137.202.0.90] X-ClientProxiedBy: svr-ies-mbx-06.mgc.mentorg.com (139.181.222.6) To svr-ies-mbx-02.mgc.mentorg.com (139.181.222.2) Subject: Re: [musl] Re: ppc64le and 32-bit LE userland compatibility On Thu, 4 Jun 2020, Daniel Kolesa wrote: > The ELFv2 document specifies things like passing of quadruple precision > floats. Indeed, VSX is needed there, but that's not a concern if you > *don't* use quadruple precision floats. My understanding is that the registers used for argument passing are all ones that exactly correspond to the Vector registers in earlier instruction set versions. In other words, you could *in principle* produce an object, or a whole libm shared library, that (a) passes or receives _Float128 values in registers, (b) does not use any instructions beyond those available with -mcpu=970, (c) would work as intended whether executed on a 970 or on POWER8 and (d) when executed on POWER8, would fully interoperate with objects receiving or passing _Float128 values and compiled for POWER8 to use VSX instructions for that purpose. GCC may not support _Float128 for older processors, but that doesn't prevent you from maintaining patches to add such support. (But if you want to support those 64-bit processors that don't have Vector registers at all, you indeed can't use binary128 and interoperate with code using VSX for that format in POWER8.) (Cf. how the Arm hard-float ABI variant works even on processors with single-precision-only VFP, because such processors still have the double-precision loads and stores although not double-precision arithmetic. When working on that ABI support in GCC some years ago, I also made sure that GNU vector types corresponding to NEON vector types were passed consistently for the hard-float ABI whether or not any vector instructions were present - thus, avoiding depending on the machine modes for those vector types because GCC could choose a different machine mode depending on the instructions available.) -- Joseph S. Myers joseph@codesourcery.com