public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47878] [4.6 Regression] 187.facerec miscompares
Date: Thu, 24 Feb 2011 11:28:00 -0000 [thread overview]
Message-ID: <bug-47878-4-gi5sSgYTQ2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47878-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47878
--- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-02-24 11:19:57 UTC ---
(In reply to comment #3)
> (In reply to comment #0)
> > I see miscompares with -O3 and -O2 -ffast-math.
>
> Does the miscompare depend on the -O flags? If so, the patch for PR 47694
> cannot have cause it as it is a libgfortran only change. Looking at the
> changelog, it then has to be a middle-end issue.
I only extracted information from our autotesters and did not run
manual tests yet. That the issue is seen across a wide range of platforms
suggests the bug is in libgfortran.
next prev parent reply other threads:[~2011-02-24 11:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 10:44 [Bug fortran/47878] New: " rguenth at gcc dot gnu.org
2011-02-24 10:56 ` [Bug fortran/47878] " rguenth at gcc dot gnu.org
2011-02-24 11:04 ` burnus at gcc dot gnu.org
2011-02-24 11:07 ` burnus at gcc dot gnu.org
2011-02-24 11:28 ` rguenth at gcc dot gnu.org [this message]
2011-02-24 11:48 ` rguenth at gcc dot gnu.org
2011-02-24 14:01 ` jvdelisle at gcc dot gnu.org
2011-02-24 14:16 ` rguenth at gcc dot gnu.org
2011-02-24 14:17 ` rguenth at gcc dot gnu.org
2011-02-24 14:26 ` rguenth at gcc dot gnu.org
2011-02-24 14:36 ` rguenth at gcc dot gnu.org
2011-02-24 14:51 ` burnus at gcc dot gnu.org
2011-02-24 14:55 ` burnus at gcc dot gnu.org
2011-02-24 15:14 ` jakub at gcc dot gnu.org
2011-02-24 15:39 ` jakub at gcc dot gnu.org
2011-02-24 16:22 ` jvdelisle at gcc dot gnu.org
2011-02-24 17:07 ` jakub at gcc dot gnu.org
2011-02-24 17:23 ` jvdelisle at gcc dot gnu.org
2011-02-24 17:41 ` jvdelisle at gcc dot gnu.org
2011-02-24 18:28 ` jakub at gcc dot gnu.org
2011-02-24 18:31 ` burnus at gcc dot gnu.org
2011-02-24 18:53 ` jvdelisle at gcc dot gnu.org
2011-02-24 18:54 ` jvdelisle at gcc dot gnu.org
2011-02-24 20:17 ` jakub at gcc dot gnu.org
2011-02-24 20:43 ` jakub at gcc dot gnu.org
2011-02-24 22:09 ` pinskia at gcc dot gnu.org
2011-02-25 10:55 ` rguenth at gcc dot gnu.org
2011-03-05 0:06 ` jvdelisle at gcc dot gnu.org
2011-03-07 3:09 ` jvdelisle at gcc dot gnu.org
2011-03-07 3:14 ` jvdelisle 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-47878-4-gi5sSgYTQ2@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).