public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/48511] Implement Steele-White algorithm for numeric output
Date: Tue, 25 Aug 2015 12:58:00 -0000 [thread overview]
Message-ID: <bug-48511-4-X7pmTkEaWe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48511-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48511
Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |fxcoudert at gcc dot gnu.org
Resolution|--- |WONTFIX
--- Comment #14 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
Seeing the PR track, it seems both Janne and Jerry are against reimplementing
Steele-White. I am too: unless we can show very good features or speed
improvement, we'd best do exactly what we do now, i.e. use the system's libc
(and possibly libquadmath). So I am closing this PR as WONTFIX.
In any case, if we wanted to have faster floating-point I/O, we should move to
something more modern than Steele-White. The current "state of the art" (as
implemented in new language runtimes, such as Julia, rust, modern javascript,
etc.) is to combine grisu3
(http://www.cs.tufts.edu/~nr/cs257/archive/florian-loitsch/printf.pdf) with
dragon4 (Steele-White) as a fall-back for the cases where grisu3 doesn't round
exactly.
prev parent reply other threads:[~2015-08-25 12:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 8:07 [Bug libfortran/48511] New: " thenlich at users dot sourceforge.net
2011-04-08 15:58 ` [Bug libfortran/48511] " jvdelisle at gcc dot gnu.org
2011-04-08 16:10 ` jvdelisle at gcc dot gnu.org
2011-04-09 21:19 ` jb at gcc dot gnu.org
2011-04-10 8:36 ` jb at gcc dot gnu.org
2011-04-10 10:20 ` thenlich at users dot sourceforge.net
2011-04-10 12:25 ` jb at gcc dot gnu.org
2011-04-27 14:17 ` thenlich at users dot sourceforge.net
2011-04-27 15:03 ` burnus at gcc dot gnu.org
2011-04-27 18:37 ` jb at gcc dot gnu.org
2011-04-28 9:30 ` jb at gcc dot gnu.org
2011-04-28 10:09 ` thenlich at users dot sourceforge.net
2011-04-29 1:42 ` jvdelisle at gcc dot gnu.org
2011-05-05 10:58 ` thenlich at users dot sourceforge.net
2015-08-25 12:58 ` fxcoudert at gcc dot gnu.org [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=bug-48511-4-X7pmTkEaWe@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).