public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "harsha dot jagasia at amd dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/37485] New: [graphite] Disconnecting exit edge in process of code generation
Date: Thu, 11 Sep 2008 20:04:00 -0000 [thread overview]
Message-ID: <bug-37485-12304@http.gcc.gnu.org/bugzilla/> (raw)
In tranlate_clast when clast stmt is a stmt_user, we can end up disconnecting
the edge that is the exit_edge of the scop that is transformed. This state
creates problems because the exit_edge no longer has a destination. Hence when
after translate_clast, the exit_edge is redirected with redirect_edge_succ, the
edge is already disconnected.
--
Summary: [graphite] Disconnecting exit edge in process of code
generation
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: harsha dot jagasia at amd dot com
GCC build triplet: x86_64-unknown-linux-gnu
GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37485
next reply other threads:[~2008-09-11 20:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 20:04 harsha dot jagasia at amd dot com [this message]
2008-09-11 20:07 ` [Bug middle-end/37485] " harsha dot jagasia at amd dot com
2008-09-12 12:57 ` grosser at gcc dot gnu dot org
2008-09-12 15:44 ` hjagasia at gcc dot gnu dot org
2008-09-12 15:46 ` hjagasia at gcc dot gnu dot org
2008-09-12 16:54 ` hjagasia at gcc dot gnu dot org
2008-09-12 16:56 ` hjagasia at gcc dot gnu dot org
2008-09-12 17:01 ` hjagasia at gcc dot gnu dot org
2008-09-13 12:44 ` rguenth at gcc dot gnu dot org
2008-09-29 13:23 ` grosser at gcc dot gnu dot org
2008-09-29 14:52 ` spop at gcc dot gnu dot org
2008-10-02 22:51 ` spop at gcc dot gnu dot org
2008-10-03 20:30 ` spop at gcc dot gnu dot org
2008-10-11 2:47 ` grosser at gcc dot gnu dot org
2008-10-11 19:28 ` spop at gcc dot gnu dot org
2008-10-15 16:27 ` spop at gcc dot gnu dot org
2008-10-15 16:29 ` spop at gcc dot gnu dot 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-37485-12304@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).