public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "grosser at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37485] [graphite] Disconnecting exit edge in process of code generation
Date: Sat, 11 Oct 2008 02:47:00 -0000 [thread overview]
Message-ID: <20081010194019.11700.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37485-12304@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from grosser at gcc dot gnu dot org 2008-10-10 19:40 -------
(In reply to comment #9)
> Subject: Re: [graphite] Disconnecting exit edge in process of code generation
>
> > Commit 140746 should have fixed Bug 3. Can you confirm this?
>
> This is a side effect of your patch.
I am sorry. With "Bug 3" I ment:
Third:
Graphite can create scops which overlap. This is an issue if one of the
overlapping scops is transformed which can cause some edges to be redirected.
When the successive overlapping scops are attempted to be transformed, the
basic blocks in the scop are no longer the same.
My commit fixed a bug, that created overlapping scops, and inserted a check for
overlapping scops. Are there any overlapping scops with the current code?
--
grosser at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |grosser at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37485
next prev parent reply other threads:[~2008-10-11 2:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 20:04 [Bug c/37485] New: " harsha dot jagasia at amd dot com
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 [this message]
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=20081010194019.11700.qmail@sourceware.org \
--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).