public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/29922] [4.3 Regression] [Linux] ICE in insert_into_preds_of_block
Date: Sat, 25 Nov 2006 09:13:00 -0000 [thread overview]
Message-ID: <20061125091321.30893.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29922-12686@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from pinskia at gcc dot gnu dot org 2006-11-25 09:13 -------
(gdb) p debug_generic_expr (vh)
VH.22
$4 = void
(gdb) p debug_generic_expr (eprime)
strlen (&lineD.1610)
(gdb) p debug_generic_expr (vuse)
lineD.1610_11
We have:
# NONLOCAL.5_14 = PHI <NONLOCAL.5_18(5)>;
# line_11 = PHI <line_17(5)>;
<L4>:;
# VUSE <line_11>;
# VUSE <NONLOCAL.5_14>;
D.1623_6 = strlen (&line);
if (D.1623_6 == 100) goto <L6>; else goto <L7>;
Though the good question is why we have those PHIs still there even though they
don't do anything except produce a copy. All the copyprop passes as far as I
can tell skip them because they are virtual.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29922
next prev parent reply other threads:[~2006-11-25 9:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 1:41 [Bug c/29922] New: gcc-4.3-20061118 failed to compile linux-2.6.19-rc6-git2 happyarch at gmail dot com
2006-11-21 2:00 ` [Bug tree-optimization/29922] " pinskia at gcc dot gnu dot org
2006-11-21 3:17 ` happyarch at gmail dot com
2006-11-21 3:22 ` pinskia at gcc dot gnu dot org
2006-11-21 3:33 ` happyarch at gmail dot com
2006-11-21 7:04 ` happyarch at gmail dot com
2006-11-21 7:10 ` pinskia at gcc dot gnu dot org
2006-11-21 7:48 ` pinskia at gcc dot gnu dot org
2006-11-21 7:50 ` pinskia at gcc dot gnu dot org
2006-11-25 9:13 ` pinskia at gcc dot gnu dot org [this message]
2006-11-27 7:52 ` [Bug tree-optimization/29922] [4.3 Regression] [Linux] ICE in insert_into_preds_of_block pinskia at gcc dot gnu dot org
2006-11-27 8:06 ` pinskia at gcc dot gnu dot org
2006-11-27 17:23 ` Andrew Pinski
2006-11-27 17:23 ` pinskia at gmail dot com
2006-12-15 22:09 ` pinskia at gcc dot gnu dot org
2006-12-18 9:33 ` pinskia at gcc dot gnu dot org
2006-12-19 21:56 ` kargl at gcc dot gnu dot org
2006-12-20 2:55 ` Daniel Berlin
2006-12-20 2:55 ` dberlin at dberlin dot org
2007-01-11 18:28 ` pinskia at gcc dot gnu dot org
2007-02-09 19:00 ` pinskia at gcc dot gnu dot org
2007-03-05 10:13 ` tbm at cyrius dot com
2007-03-09 17:55 ` dberlin at gcc dot gnu dot org
2007-03-09 19:28 ` tbm at cyrius dot com
2007-03-09 19:34 ` tbm at cyrius dot com
2007-03-10 8:48 ` Jean-pierre dot vial at wanadoo dot fr
2007-03-17 23:08 ` dberlin at gcc dot gnu dot org
2007-03-17 23:17 ` tbm at cyrius dot com
2007-03-17 23:19 ` dberlin at gcc dot gnu dot org
2007-04-28 4:19 ` kargl 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=20061125091321.30893.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).