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 29830 invoked from network); 5 Jun 2021 22:05:29 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 5 Jun 2021 22:05:29 -0000 Received: (qmail 17887 invoked by uid 550); 5 Jun 2021 22:05:27 -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 17866 invoked from network); 5 Jun 2021 22:05:26 -0000 Date: Sat, 5 Jun 2021 18:05:14 -0400 From: Rich Felker To: Arnd Bergmann Cc: musl@lists.openwall.com Message-ID: <20210605220514.GH13220@brightrain.aerifal.cx> References: <20210605171216.GA7558@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] Adding PowerPC SPE support On Sat, Jun 05, 2021 at 11:15:04PM +0200, Arnd Bergmann wrote: > On Sat, Jun 5, 2021 at 7:12 PM Rich Felker wrote: > > > > When the soft-float ABI for PowerPC was added in 2016 (commit > > 5a92dd95c77cee81755f1a441ae0b71e3ae2bcdb, mail thread "[PATCH v3] Add > > PowerPC soft-float support") with Freescale cpus having the > > alternative SPE FPU as the main use case, I noted that we could > > probably support hard float on them, but that it would involve > > determining some difficult ABI constraints. I'm now revisiting adding > > this support. > > Note that regardless of the technical issues, there is a practical problem > in the long run, since gcc-8.5 was the last release with powerpcspe > support, and at some point in the future everyone will move to gcc-9 > or higher. Yes, llvm has added it though and presumably ppl who want it will just use clang or stick with old gcc (which makes me sad, but that's how it is). Rich