public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <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: Sat, 23 Apr 2011 16:33:00 -0000	[thread overview]
Message-ID: <bug-48615-4-GWCmKMTQeu@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

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot       |jvdelisle at gcc dot
                   |gnu.org                     |gnu.org

--- Comment #5 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2011-04-23 16:32:16 UTC ---
Created attachment 24082
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24082
Preliminary patch

Here is just a experimental patch. Yes we could do some things in output float.
 I will think a bit on that.  The patch also has adjustments to default widths.
The default widths require quite a few test suite adjustments, which I have in
my tree and will post later to pr48488.

I believe the intent of this code block in write_float was to reduce the number
of digits converted in the later snprintf calls as a simple optimization.


  parent reply	other threads:[~2011-04-23 16:33 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 [this message]
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
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-GWCmKMTQeu@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).