public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55539] [4.8 Regression] -fno-sign-zero may generate output with the wrong sign
Date: Sat, 15 Dec 2012 16:36:00 -0000	[thread overview]
Message-ID: <bug-55539-4-5JxoEf0ADD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55539-4@http.gcc.gnu.org/bugzilla/>


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

Janne Blomqvist <jb at gcc dot gnu.org> changed:

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

--- Comment #5 from Janne Blomqvist <jb at gcc dot gnu.org> 2012-12-15 16:36:08 UTC ---
Patch: http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01011.html

Although Harald's patch fixed the issue for me as well, I opted for a slightly
different approach. The regression crept in because in the old code we had
removed the decimal point, whereas in the current code it may be included in
the string we're investigating.


  parent reply	other threads:[~2012-12-15 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 22:11 [Bug fortran/55539] New: [4.8 Regression] -fno-sign-zero may generate wrong formatted output anlauf at gmx dot de
2012-11-30 21:24 ` [Bug fortran/55539] " dominiq at lps dot ens.fr
2012-11-30 21:48 ` [Bug fortran/55539] [4.8 Regression] -fno-sign-zero may generate output with the wrong sign burnus at gcc dot gnu.org
2012-12-11 22:33 ` anlauf at gmx dot de
2012-12-12 11:16 ` burnus at gcc dot gnu.org
2012-12-15 16:36 ` jb at gcc dot gnu.org [this message]
2012-12-15 16:48 ` jb at gcc dot gnu.org
2012-12-25 22:11 ` jb at gcc dot gnu.org
2012-12-25 22:22 ` jb 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-55539-4-5JxoEf0ADD@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).