mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Stdio resource usage
Date: Wed, 20 Feb 2019 12:13:41 -0500	[thread overview]
Message-ID: <20190220171341.GC23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190220163759.GV21289@port70.net>

On Wed, Feb 20, 2019 at 05:37:59PM +0100, Szabolcs Nagy wrote:
> * 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.

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


  reply	other threads:[~2019-02-20 17:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 23:34 Nick Bray
2019-02-20  2:43 ` Rich Felker
2019-02-20 10:49   ` Szabolcs Nagy
2019-02-20 15:47     ` Markus Wichmann
2019-02-20 16:37       ` Szabolcs Nagy
2019-02-20 17:13         ` Rich Felker [this message]
2019-02-20 18:34       ` A. Wilcox
2019-02-20 19:11         ` Markus Wichmann
2019-02-20 19:24           ` Rich Felker
2019-02-21 16:09             ` Markus Wichmann
2019-02-21 16:27               ` Jens Gustedt
2019-02-21 17:02               ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190220171341.GC23599@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).