public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/21718] real.c rounding not perfect
Date: Wed, 20 Nov 2013 14:39:00 -0000	[thread overview]
Message-ID: <bug-21718-4-8jBFcUv8q4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-21718-4@http.gcc.gnu.org/bugzilla/>

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

Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |4.9.0

--- Comment #22 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Fixed for 4.9, at least if MPFR 3.1.1p2 or later is used (I don't know if the
bug with mpfr_strtofr ternary value in older versions would affect the way
mpfr_strtofr is now used in GCC, rounding towards zero with a higher precision
and using the ternary value to set a sticky bit if the value was inexact, so
that GCC's final rounding to the destination format is correct).


  parent reply	other threads:[~2013-11-20 14:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-21718-4@http.gcc.gnu.org/bugzilla/>
2012-11-04 23:06 ` hjl.tools at gmail dot com
2012-11-05  0:17 ` vincent-gcc at vinc17 dot net
2012-11-05  1:38 ` hjl.tools at gmail dot com
2012-11-05  8:12 ` vincent-gcc at vinc17 dot net
2012-11-05 20:49 ` joseph at codesourcery dot com
2013-09-25 14:48 ` exploringbinary at gmail dot com
2013-09-25 15:45 ` vincent-gcc at vinc17 dot net
2013-09-25 18:00 ` exploringbinary at gmail dot com
2013-10-09 18:58 ` exploringbinary at gmail dot com
2013-10-10  1:12 ` vincent-gcc at vinc17 dot net
2013-11-20 14:35 ` jsm28 at gcc dot gnu.org
2013-11-20 14:39 ` jsm28 at gcc dot gnu.org [this message]
2013-11-20 14:41 ` jsm28 at gcc dot gnu.org
2013-11-20 15:07 ` exploringbinary at gmail dot com
2013-11-21 19:34 ` exploringbinary at gmail dot com
2013-11-21 23:04 ` exploringbinary at gmail dot com
2013-11-21 23:20 ` jsm28 at gcc dot gnu.org
2013-11-22  5:22 ` exploringbinary at gmail dot com
2013-11-26  2:50 ` exploringbinary at gmail dot com
     [not found] <bug-21718-6@http.gcc.gnu.org/bugzilla/>
2005-10-29 20:50 ` pinskia at gcc dot gnu dot org
2007-02-05 19:03 ` jsm28 at gcc dot gnu dot org
2007-10-11  3:45 ` neil at gcc dot gnu dot org
2007-10-18 15:24 ` neil at gcc dot gnu dot org
2009-04-20 17:02 ` ghazi at gcc dot gnu dot org
2009-04-20 17:31 ` joseph at codesourcery dot com
2010-06-04  1:31 ` exploringbinary at gmail dot com
2010-06-05 11:57 ` joseph at codesourcery dot com
2005-05-23 13:03 [Bug c/21718] New: " neil at gcc dot gnu dot org
2005-05-23 13:05 ` [Bug middle-end/21718] " pinskia at gcc dot gnu dot org
2005-05-23 14:50 ` jsm28 at gcc dot gnu dot org
2005-05-24  2:59 ` jsm28 at gcc dot gnu dot 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-21718-4-8jBFcUv8q4@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).