From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13825
Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail
From: Szabolcs Nagy <nsz@port70.net>
Newsgroups: gmane.linux.lib.musl.general
Subject: Re: Stdio resource usage
Date: Wed, 20 Feb 2019 17:37:59 +0100
Message-ID: <20190220163759.GV21289@port70.net>
References: <20190220104901.GU21289@port70.net>
 <20190220154740.GD19969@voyager>
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="27325"; mail-complaints-to="usenet@blaine.gmane.org"
User-Agent: Mutt/1.10.1 (2018-07-13)
To: musl@lists.openwall.com
Original-X-From: musl-return-13841-gllmg-musl=m.gmane.org@lists.openwall.com Wed Feb 20 17:38:15 2019
Return-path: <musl-return-13841-gllmg-musl=m.gmane.org@lists.openwall.com>
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 <musl-return-13841-gllmg-musl=m.gmane.org@lists.openwall.com>)
	id 1gwUsv-00070V-Ih
	for gllmg-musl@m.gmane.org; Wed, 20 Feb 2019 17:38:13 +0100
Original-Received: (qmail 23793 invoked by uid 550); 20 Feb 2019 16:38:11 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Original-Received: (qmail 23773 invoked from network); 20 Feb 2019 16:38:10 -0000
Mail-Followup-To: musl@lists.openwall.com
Content-Disposition: inline
In-Reply-To: <20190220154740.GD19969@voyager>
Xref: news.gmane.org gmane.linux.lib.musl.general:13825
Archived-At: <http://permalink.gmane.org/gmane.linux.lib.musl.general/13825>

* Markus Wichmann <nullplan@gmx.net> [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.