From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] floatfmt on 64-bit targets?
Date: Wed, 26 Oct 2005 11:25:30 +0100 [thread overview]
Message-ID: <788ac2c09f34fc1a4ce43b2316581314@vitanuova.com> (raw)
In-Reply-To: <20051025215838.GA3159@mero.morphisms.net>
[-- Attachment #1: Type: text/plain, Size: 63 bytes --]
was that on Plan 9 or plan 9 ports (and if so, which platform)?
[-- Attachment #2: Type: message/rfc822, Size: 2582 bytes --]
From: William Josephson <jkw@eecs.harvard.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] floatfmt on 64-bit targets?
Date: Tue, 25 Oct 2005 17:58:38 -0400
Message-ID: <20051025215838.GA3159@mero.morphisms.net>
Has anyone run into problems with %f on 64-bit targets?
With large numbers passed in to %f, it appears xdtoa
overruns s in floatfmt. Has anyone already fixed this?
next prev parent reply other threads:[~2005-10-26 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 21:58 William Josephson
2005-10-25 23:35 ` jmk
2005-10-26 10:25 ` C H Forsyth [this message]
2005-10-26 16:31 ` William Josephson
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=788ac2c09f34fc1a4ce43b2316581314@vitanuova.com \
--to=forsyth@vitanuova.com \
--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).