From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13826 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Stdio resource usage Date: Wed, 20 Feb 2019 12:13:41 -0500 Message-ID: <20190220171341.GC23599@brightrain.aerifal.cx> References: <20190220104901.GU21289@port70.net> <20190220154740.GD19969@voyager> <20190220163759.GV21289@port70.net> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="195782"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-13842-gllmg-musl=m.gmane.org@lists.openwall.com Wed Feb 20 18:13:59 2019 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.89) (envelope-from ) id 1gwVRV-000onP-OL for gllmg-musl@m.gmane.org; Wed, 20 Feb 2019 18:13:57 +0100 Original-Received: (qmail 28283 invoked by uid 550); 20 Feb 2019 17:13:55 -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 28265 invoked from network); 20 Feb 2019 17:13:55 -0000 Content-Disposition: inline In-Reply-To: <20190220163759.GV21289@port70.net> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:13826 Archived-At: On Wed, Feb 20, 2019 at 05:37:59PM +0100, Szabolcs Nagy wrote: > * Markus Wichmann [2019-02-20 16:47:40 +0100]: > > On Wed, Feb 20, 2019 at 11:49:01AM +0100, Szabolcs Nagy wrote: > > > aarch64 has 128 bit fp regs, so in principle future arch extension > > > may add 128bit instructions without breaking abi. (which may happen > > > if aarch64 gets adoption in supercomputers, e.g. powerpc64 did that) > > > > > > > Say, if IEEE quad is causing problems, wouldn't it be possible to > > compile a tool chain with long double == double for the time being? > > of course if you are writing your own os you can do all sorts of things, > but toolchains will follow the pcs abi in general which says that > long double == ieee binary128 > > e.g. gcc does not have a config option to turn long double type into > binary64 on aarch64. so you would have to maintain your own gcc fork. One thing I think we could consider doing in musl is extract the long double significand via the representation rather than math, and using float_t rather than long double for the rounding probes. However I'm not clear that most of the soft float machinery wouldn't already be pulled in via the promotion of double args to long double for storage in the arg structure... Also hex float would need new code I think. Rich