mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: 32-bit double and long double
Date: Mon, 26 Nov 2018 12:03:39 -0500	[thread overview]
Message-ID: <20181126170339.GO23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <87va4j3lpr.fsf@southeast>

On Mon, Nov 26, 2018 at 06:25:04PM +0300, Eugene Sharygin wrote:
> Hi,
> 
> We're using Musl on a platform where both float, double, and long double
> are in IEEE-754 binary32 format, and I'm wondering if a patch that lifts
> some of the assumptions made regarding widths of floating-point types
> would be accepted.

No, musl only supports (roughly) Annex-F conforming environments, with
IEEE single and double and a long double type with IEEE-compatible
semantics. Such patches won't be accepted upstream.

Is there a reason your target is defining double in an unuseful and
incompatible way rather than doing hard-single and soft-double? If you
have any control over the choice of ABI, I think the latter makes a
lot more sense.

Rich


> Here is the relevant excerpt from the documentation:
> 
> > Floating-point formats are assumed to be IEEE-754 binary32 format for
> > float and IEEE-754 binary64 for double.
> >
> > Supported long double formats: IEEE-754 binary64 (ld64) and x86 80 bit
> > extended precision format (ld80) are fully supported and there is
> > partial support for IEEE-754 binary128 (ld128).
> 
> Eugene


  reply	other threads:[~2018-11-26 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 15:25 Eugene Sharygin
2018-11-26 17:03 ` Rich Felker [this message]
2018-11-26 17:30   ` Eugene Sharygin
2018-11-26 17:35   ` Eugene Sharygin
2018-11-26 17:36   ` Jon Chesterfield
2018-11-26 18:19     ` Szabolcs Nagy
2018-11-27  2:32     ` Rich Felker
2018-11-27 12:52       ` Szabolcs Nagy

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=20181126170339.GO23599@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).