From: "writeonce@midipix.org" <writeonce@midipix.org>
To: musl@lists.openwall.com
Subject: Re: checks involving LDBL_MANT_DIG
Date: Tue, 27 May 2014 18:37:19 +0300 [thread overview]
Message-ID: <5384B12F.5010909@midipix.org> (raw)
In-Reply-To: <20140527150038.GM12324@port70.net>
On 05/27/2014 06:00 PM, Szabolcs Nagy wrote:
> * writeonce@midipix.org <writeonce@midipix.org> [2014-05-27 07:23:20 -0700]:
>> In src/complex/*, several files check for LDBL_MANT_DIG == 53 &&
>> LDBL_MAX_EXP == 1024, however according to src/stdio/vfprintf.c,
>> (LDBL_MANT_DIG == 53) is considered incorrect and would cause a
>> compile-time error. Does this mean that the above checks in
>> src/complex/* may be eliminated?
> there is nothing wrong with LDBL_MANT_DIG == 53
>
> vfprintf only checks if long double really has appropriate size in that case
>
>
Thanks, that explains everything... wrong experiment on my part.
zg
prev parent reply other threads:[~2014-05-27 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 14:23 writeonce
2014-05-27 15:00 ` Szabolcs Nagy
2014-05-27 15:37 ` writeonce [this message]
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=5384B12F.5010909@midipix.org \
--to=writeonce@midipix.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).