From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13393 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: [PATCH] PPC64 IEEE128 bit FP support Date: Fri, 2 Nov 2018 12:13:35 -0400 Message-ID: <20181102161335.GL5150@brightrain.aerifal.cx> References: <20181026042829.GB28637@voyager> <20181026130119.GD3880@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1541175103 20791 195.159.176.226 (2 Nov 2018 16:11:43 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 2 Nov 2018 16:11:43 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-13409-gllmg-musl=m.gmane.org@lists.openwall.com Fri Nov 02 17:11:39 2018 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1gIc2s-0005LA-WD for gllmg-musl@m.gmane.org; Fri, 02 Nov 2018 17:11:39 +0100 Original-Received: (qmail 1235 invoked by uid 550); 2 Nov 2018 16:13:48 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 1213 invoked from network); 2 Nov 2018 16:13:47 -0000 Content-Disposition: inline In-Reply-To: <20181026130119.GD3880@port70.net> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:13393 Archived-At: On Fri, Oct 26, 2018 at 03:01:20PM +0200, Szabolcs Nagy wrote: > * Markus Wichmann [2018-10-26 06:28:29 +0200]: > > Now you just need to look through all the maths code to find all the > > places that need changing. __floatscan() comes to mind immediately. And > > I don't know if any of the libm functions needs adjustment for this new > > format. > > generic c code in musl should work for all supported > floating-point formats, which includes ieee binary128 > for long double. > > only float.h needs to be set up according to the abi. > > some long double math functions don't have high quality > implementations for ieee binary128 format though. Yes. Assuming there aren't other problems revealed by my questions about argument passing and ISA levels, I think the only blocking issue here is naming the ABI. I forgot to mention but that should also involve a gcc patch that we can put in mcm and eventually upstream. QoI issues for IEEE-quad-based [sub]archs can be improved later; aarch64 and s390x are already affected IIRC. Rich