public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thenlich at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/48615] Invalid UP/DOWN rounding with E and ES descriptors
Date: Mon, 25 Apr 2011 08:44:00 -0000	[thread overview]
Message-ID: <bug-48615-4-NUQVldwNjz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48615-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48615

--- Comment #12 from Thomas Henlich <thenlich at users dot sourceforge.net> 2011-04-25 08:43:32 UTC ---
The patch submitted to the list is different to the one I based my comments on.
My mistake.

Good work.

With the current method of letting printf do the conversion, there seems to be
no better way than always converting the full 40 digits, and then throwing away
most of them.

In Bug 48511 David Gay's dtoa implementation was mentioned. I looked into that
and I think it can be modified to be fully Fortran standard compliant. It
combines digit generation and rounding in one step and is probably
significantly more efficient than our current solution. Will investigate
further.


  parent reply	other threads:[~2011-04-25  8:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15  7:08 [Bug libfortran/48615] New: " thenlich at users dot sourceforge.net
2011-04-23  7:49 ` [Bug libfortran/48615] " thenlich at users dot sourceforge.net
2011-04-23 11:07 ` thenlich at users dot sourceforge.net
2011-04-23 12:24 ` jvdelisle at gcc dot gnu.org
2011-04-23 13:20 ` thenlich at users dot sourceforge.net
2011-04-23 16:33 ` jvdelisle at gcc dot gnu.org
2011-04-23 17:04 ` thenlich at users dot sourceforge.net
2011-04-24 20:34 ` jvdelisle at gcc dot gnu.org
2011-04-24 21:41 ` thenlich at users dot sourceforge.net
2011-04-24 23:24   ` Jerry DeLisle
2011-04-24 23:25 ` jvdelisle at frontier dot com
2011-04-24 23:43 ` jvdelisle at gcc dot gnu.org
2011-04-24 23:54 ` jvdelisle at frontier dot com
2011-04-25  8:44 ` thenlich at users dot sourceforge.net [this message]
2011-04-29 15:03 ` jvdelisle at gcc dot gnu.org
2011-04-29 15:11 ` jvdelisle at gcc dot gnu.org
2011-05-06 20:14 ` jvdelisle at gcc dot gnu.org
2013-01-06 14:13 ` burnus at gcc dot gnu.org

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-48615-4-NUQVldwNjz@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).