From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] libfmt/libutf and long double
Date: Mon, 29 Dec 2003 22:30:44 -0500 [thread overview]
Message-ID: <e227eef870423524550ae61ca03ecc24@plan9.bell-labs.com> (raw)
In-Reply-To: <C01AD478-3A75-11D8-BD48-000A95C53D8A@suspicious.org>
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
Could it be that we don't know squat about long double? At least in
our plan9 ape library, we just assume that the 'E' arg is a double
and don't look at the ll flags. I don't know about the Unix libfmt.
Look at __efgfmt in fltfmt.c and see what the expected arg is.
[-- Attachment #2: Type: message/rfc822, Size: 2442 bytes --]
From: suspect@suspicious.org
To: 9fans@cse.psu.edu
Subject: [9fans] libfmt/libutf and long double
Date: Mon, 29 Dec 2003 22:10:41 -0500
Message-ID: <C01AD478-3A75-11D8-BD48-000A95C53D8A@suspicious.org>
Hello,
I've run into a behavior with libfmt/libutf on UNIX system
that does not seem intuitive:
long double ldv = 3.3;
print("long double var = %llE\n", ldv);
gives:
long double var = -6.257775E+92
Identical code under Plan 9 gives the expected output of:
long double var = 3.300000E+00
Is there any particular reason why the behaviors should
differ in this manner ?
cheers,
next prev parent reply other threads:[~2003-12-30 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 3:10 suspect
2003-12-30 3:30 ` David Presotto [this message]
2003-12-31 16:17 ` Russ Cox
2003-12-31 18:43 ` suspect
2003-12-31 19:11 ` David Presotto
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=e227eef870423524550ae61ca03ecc24@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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.
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).