public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/26626] [4.2 Regression] ICE in in add_virtual_operand
Date: Fri, 10 Mar 2006 11:10:00 -0000 [thread overview]
Message-ID: <20060310111044.21969.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26626-12049@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from rguenth at gcc dot gnu dot org 2006-03-10 11:10 -------
<L2>:;
pretmp.23_2 = (union U *) &rv;
# NMT.6_4 = PHI <NMT.6_5(2), NMT.6_6(5)>;
ovfl:;
rv.0_1 = pretmp.23_2;
# NMT.6_6 = V_MAY_DEF <NMT.6_4>;
rv.0_1->d = 42;
# VUSE <NMT.6_6>;
D.1529_3 = rv.0_1->L;
if (D.1529_3 != 0) goto <L5>; else goto <L1>;
<L5>:;
goto <bb 3> (ovfl);
we prop pretmp.23_2 to rv.0_1 in rv.0_1->d = 42 -- but we don't have the
NMT associated with pretmp.23_2:
$5 = {pt_anything = 0, value_escapes_p = 0, is_dereferenced = 0,
pt_global_mem = 0, pt_null = 0, pt_vars = 0xb7dec890, name_mem_tag = 0x0,
escape_mask = 0}
As we have in alias after PRE:
Pointed-to sets for pointers in breakme
pretmp.23_2, points-to vars: { rv }
rv.0_1, name memory tag: NMT.6, is dereferenced, points-to vars: { rv }
which looks inconsistent.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26626
next prev parent reply other threads:[~2006-03-10 11:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 22:40 [Bug tree-optimization/26626] New: " mueller at gcc dot gnu dot org
2006-03-09 22:40 ` [Bug tree-optimization/26626] " mueller at gcc dot gnu dot org
2006-03-09 22:52 ` [Bug tree-optimization/26626] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-03-09 22:54 ` pinskia at gcc dot gnu dot org
2006-03-09 23:31 ` Daniel Berlin
2006-03-09 23:31 ` dberlin at dberlin dot org
2006-03-09 23:58 ` pinskia at gcc dot gnu dot org
2006-03-10 0:39 ` dberlin at dberlin dot org
2006-03-10 10:40 ` rguenth at gcc dot gnu dot org
2006-03-10 10:51 ` mueller at gcc dot gnu dot org
2006-03-10 11:10 ` rguenth at gcc dot gnu dot org [this message]
2006-03-13 16:17 ` mueller at gcc dot gnu dot org
2006-03-13 16:52 ` dberlin at dberlin dot org
2006-03-13 16:56 ` mueller at gcc dot gnu dot org
2006-04-02 13:09 ` fxcoudert at gcc dot gnu dot org
2006-04-10 16:35 ` pinskia at gcc dot gnu dot org
2006-04-27 13:14 ` fxcoudert at gcc dot gnu dot org
2006-04-27 15:39 ` dberlin at dberlin dot org
2006-04-27 16:43 ` rguenth at gcc dot gnu dot org
2006-04-27 16:55 ` dberlin at dberlin dot org
2006-04-27 16:56 ` rguenth at gcc dot gnu dot org
2006-04-27 17:08 ` rguenth at gcc dot gnu dot org
2006-04-28 18:26 ` dannyb at google dot com
2006-05-03 3:19 ` dberlin at gcc dot gnu dot org
2006-05-03 13:02 ` mueller at gcc dot gnu dot org
2006-05-03 14:15 ` dberlin at dberlin 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=20060310111044.21969.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).