public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/60418] [4.9 Regression] 435.gromacs in SPEC CPU 2006 is miscompiled
Date: Wed, 12 Mar 2014 08:54:00 -0000	[thread overview]
Message-ID: <bug-60418-4-u2YrrfJskH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60418-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #27 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
  basic_block bbb = gimple_bb (SSA_NAME_DEF_STMT (oea->op));
in the patch contains a pasto, which I guess can explain most if not all the
-fcompare-debug failures.  That said, thinking more about it, there still could
be -fcompare-debug differences, because debug stmts also get uids and sometimes
when inserting stmts the previous stmt uid is used, sometimes next stmt uid, so
we probably should use reassoc_stmt_dominates_stmt_p.


  parent reply	other threads:[~2014-03-12  8:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 22:37 [Bug middle-end/60418] New: " hjl.tools at gmail dot com
2014-03-04 23:31 ` [Bug middle-end/60418] " hjl.tools at gmail dot com
2014-03-05  9:32 ` rguenth at gcc dot gnu.org
2014-03-05  9:33 ` rguenth at gcc dot gnu.org
2014-03-05  9:36 ` rguenth at gcc dot gnu.org
2014-03-05 19:10 ` hjl.tools at gmail dot com
2014-03-05 19:18 ` hjl.tools at gmail dot com
2014-03-05 20:08 ` hjl.tools at gmail dot com
2014-03-05 20:45 ` hjl.tools at gmail dot com
2014-03-06 18:45 ` hjl.tools at gmail dot com
2014-03-06 21:56 ` hjl.tools at gmail dot com
2014-03-06 23:29 ` hjl.tools at gmail dot com
2014-03-07  9:15 ` rguenth at gcc dot gnu.org
2014-03-07  9:18 ` rguenth at gcc dot gnu.org
2014-03-07 21:57 ` hjl.tools at gmail dot com
2014-03-07 22:12 ` jakub at gcc dot gnu.org
2014-03-07 23:12 ` hjl.tools at gmail dot com
2014-03-08  9:49 ` rguenther at suse dot de
2014-03-10 10:28 ` jakub at gcc dot gnu.org
2014-03-10 13:27 ` rguenther at suse dot de
2014-03-10 15:46 ` hjl.tools at gmail dot com
2014-03-10 16:36 ` jakub at gcc dot gnu.org
2014-03-10 17:01 ` hjl.tools at gmail dot com
2014-03-11  8:49 ` rguenther at suse dot de
2014-03-11 15:06 ` hjl.tools at gmail dot com
2014-03-11 17:47 ` jakub at gcc dot gnu.org
2014-03-11 21:03 ` hjl.tools at gmail dot com
2014-03-12  8:54 ` jakub at gcc dot gnu.org [this message]
2014-03-12  8:54 ` rguenther at suse dot de
2014-03-12  9:13 ` jakub at gcc dot gnu.org
2014-03-12 15:29 ` hjl.tools at gmail dot com
2014-03-13  9:39 ` jakub at gcc dot gnu.org
2014-03-13  9:40 ` jakub 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-60418-4-u2YrrfJskH@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).