public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/68013] [6 Regression] ICE on valid code at -O2 on x86_64-linux-gnu in duplicate_thread_path, at tree-ssa-threadupdate.c:2469
Date: Mon, 26 Oct 2015 15:26:00 -0000	[thread overview]
Message-ID: <bug-68013-4-6tL4oh6YuJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68013-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68013

Jeffrey A. Law <law at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2015-10-26
     Ever confirmed|0                           |1

--- Comment #1 from Jeffrey A. Law <law at redhat dot com> ---
The problem here is the first block in an FSM path may not be added to
VISITED_BBs.  That in turn results in the threader finding a path which passes
through that initial block a second time, reaching a different destination the
second time through.

This is caught by the assertion (to avoid generating incorrect code).  Fixing
is simple.  But...

I'm not real happy with how the affected code is structured, but I'm at a loss
right now how to reorganize it in the immediate term.  I'm hoping to get some
clarity as I continue to look to replace the EDGE_DFS_BACK support in the old
threader with the FSM threader.

Anyway, I'll be committing a fix shortly.


  parent reply	other threads:[~2015-10-26 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19  3:24 [Bug tree-optimization/68013] New: " su at cs dot ucdavis.edu
2015-10-19  9:59 ` [Bug tree-optimization/68013] [6 Regression] " rguenth at gcc dot gnu.org
2015-10-26 15:26 ` law at redhat dot com [this message]
2015-10-26 15:36 ` law at gcc dot gnu.org
2015-10-26 15:37 ` law at redhat dot com

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-68013-4-6tL4oh6YuJ@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).