public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/52173] internal compiler error: verify_ssa failed possibly caused by itm
Date: Thu, 20 Sep 2012 15:09:00 -0000 [thread overview]
Message-ID: <bug-52173-4-xsJs0MY7d2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52173-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52173
--- Comment #11 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-09-20 15:08:55 UTC ---
(In reply to comment #10)
> On Wed, 19 Sep 2012, aldyh at gcc dot gnu.org wrote:
>
> > After loop unrolling the above remains unchanged, but the following is inserted
> > *before* bb 3. [Note, the following is after update_ssa(TODO_update_ssa), but
> > before cleanup_tree_cfg() for clarity.]
> >
> > <bb 8>:
> > # .MEM_12 = PHI <.MEM_3(D)(2)>
> > # ivtmp_5 = PHI <10(2)>
> > # .MEM_6 = VDEF <.MEM_13> <-- *************************** -->
> > ^^^^^^^^^^^^ <-- shouldn't this be <.MEM_12> ?????
> > <-- *************************** -->
>
> Yes.
Btw, is_new_name says yes to .MEM_12, false for .MEM_6 and 13. update_ssa
should have adjusted the use .MEM_13 to .MEM_12, but it didn't for some
reason.
I see that the DEF stmt for .MEM_6 is
# .MEM_59 = VDEF <.MEM_13>
__transaction_relaxed // SUBCODE=[ GTMA_HAVE_STORE ]
though before update_ssa. That looks bogus to me.
Now I have to leave ... maybe the above is some hints to you (or I will
try to look further tomorrow).
next prev parent reply other threads:[~2012-09-20 15:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 15:51 [Bug middle-end/52173] New: " lloyd at randombit dot net
2012-02-08 15:53 ` [Bug middle-end/52173] " lloyd at randombit dot net
2012-02-08 15:54 ` lloyd at randombit dot net
2012-02-15 3:50 ` regehr at cs dot utah.edu
2012-02-15 3:54 ` pinskia at gcc dot gnu.org
2012-02-15 3:58 ` regehr at cs dot utah.edu
2012-08-13 6:57 ` jakub at gcc dot gnu.org
2012-09-12 19:53 ` aldyh at gcc dot gnu.org
2012-09-12 19:53 ` aldyh at gcc dot gnu.org
2012-09-14 21:20 ` aldyh at gcc dot gnu.org
2012-09-19 19:44 ` aldyh at gcc dot gnu.org
2012-09-20 7:44 ` rguenther at suse dot de
2012-09-20 15:09 ` rguenth at gcc dot gnu.org [this message]
2012-09-21 8:56 ` rguenth at gcc dot gnu.org
2012-09-21 12:39 ` rguenth at gcc dot gnu.org
2012-09-21 13:28 ` rguenth at gcc dot gnu.org
2012-09-21 13:30 ` rguenth at gcc dot gnu.org
2012-09-24 8:57 ` rguenth at gcc dot gnu.org
2012-09-24 8:58 ` rguenth at gcc dot gnu.org
2012-11-28 20:57 ` aldyh at gcc dot gnu.org
2012-11-28 20:58 ` aldyh 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-52173-4-xsJs0MY7d2@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).