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/46499] [4.5/4.6 Regression] gcc.c-torture/execute/20051021-1.c FAILs with -fno-tree-dominator-opts -fno-tree-ccp
Date: Mon, 22 Nov 2010 14:17:00 -0000	[thread overview]
Message-ID: <bug-46499-4-oOUORK7zl3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46499-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-11-22 14:10:16 UTC ---
Created attachment 22483
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22483
gcc46-pr46499.patch

Untested fix.  We have since last:
(jump_insn 8 7 9 (set (pc)
        (label_ref 0)) pr46499-1.c:26 -1
     (nil))

(barrier 9 8 10)

(jump_insn 10 9 11 (set (pc)
        (label_ref 0)) pr46499-1.c:26 -1
     (nil))

(barrier 11 10 0)

and maybe_cleanup_end_of_basic_block, as it sees there is no drop through label
and thus all jumps must go to the other edge, decides to remove the first jump,
but doesn't remove the barrier right after it, and a barrier left in the middle
of a bb after no insn that could cause the barrier of course confuses
everything and is wrong, because we really want to jump to the target label
instead of assuming the spot is never reachable.


  parent reply	other threads:[~2010-11-22 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 15:45 [Bug tree-optimization/46499] New: " zsojka at seznam dot cz
2010-11-16 15:59 ` [Bug tree-optimization/46499] " zsojka at seznam dot cz
2010-11-16 16:06 ` [Bug tree-optimization/46499] [4.5/4.6 Regression] " rguenth at gcc dot gnu.org
2010-11-22 14:00 ` [Bug middle-end/46499] " jakub at gcc dot gnu.org
2010-11-22 14:17 ` jakub at gcc dot gnu.org [this message]
2010-11-23 15:34 ` jakub at gcc dot gnu.org
2010-11-25 16:10 ` rguenth at gcc dot gnu.org
2010-11-26 22:10 ` [Bug middle-end/46499] [4.5 " jakub at gcc dot gnu.org
2010-12-07 15:23 ` jakub at gcc dot gnu.org
2010-12-07 15:44 ` 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-46499-4-oOUORK7zl3@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).