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/22483] [4.1 Regression] ICE : tree check: expected ssa_name, have var_decl in is_old_name, at tree-into-ssa.c:466
Date: Fri, 15 Jul 2005 20:45:00 -0000	[thread overview]
Message-ID: <20050715203958.12251.qmail@sourceware.org> (raw)
In-Reply-To: <20050714122637.22483.sylvain.pion@sophia.inria.fr>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-15 20:39 -------
Here is the backtrace:
#0  internal_error (gmsgid=0xb7eb64 "tree check: %s, have %s in %s, at %s:%d") at ../../gcc/
diagnostic.c:534
#1  0x008f46c0 in tree_check_failed (node=0x4bf6d20, file=0xb54ecc "../../gcc/tree-into-ssa.c", 
line=466, function=0xbc3e38 "is_old_name") at ../../gcc/tree.c:5778
#2  0x0031548c in is_old_name (name=0x4bf6d20) at ../../gcc/tree-into-ssa.c:466
#3  0x00315b38 in maybe_replace_use (use_p=0x4b77bd8) at ../../gcc/tree-into-ssa.c:1383
#4  0x0031592c in rewrite_update_stmt (walk_data=0xbffff3e8, bb=0x474e3f0, si={tsi = {ptr = 
0x2ecc400, container = 0x433ee40}, bb = 0x474e3f0}) at ../../gcc/tree-into-ssa.c:1471
#5  0x0035e01c in walk_dominator_tree (walk_data=0xbffff3e8, bb=0x474e3f0) at ../../gcc/
domwalk.c:196
#6  0x0035e0dc in walk_dominator_tree (walk_data=0xbffff3e8, bb=0x474e230) at ../../gcc/
domwalk.c:212
#7  0x00316274 in rewrite_blocks (entry=0x474e230, what=REWRITE_UPDATE, blocks=0x2b06bc0) at 
../../gcc/tree-into-ssa.c:1617
#8  0x0031a6e4 in update_ssa (update_flags=128) at ../../gcc/tree-into-ssa.c:2799


We have a SFT at this point.  For some reason symbol_marked_for_renaming (sym) is returning 0 which 
is wrong.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dberlin at gcc dot gnu dot
                   |                            |org
  GCC build triplet|i686-pc-linux-gnu           |
   GCC host triplet|i686-pc-linux-gnu           |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22483


  parent reply	other threads:[~2005-07-15 20:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 12:28 [Bug tree-optimization/22483] New: " sylvain dot pion at sophia dot inria dot fr
2005-07-14 12:47 ` [Bug tree-optimization/22483] " sylvain dot pion at sophia dot inria dot fr
2005-07-14 13:58 ` [Bug tree-optimization/22483] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-07-14 16:53 ` reichelt at gcc dot gnu dot org
2005-07-15 20:45 ` pinskia at gcc dot gnu dot org [this message]
2005-07-15 20:57 ` dberlin at dberlin dot org
2005-07-16 18:59 ` pinskia at gcc dot gnu dot org
2005-07-17  1:38 ` dberlin at dberlin dot org
2005-07-17 10:00 ` sylvain dot pion at sophia dot inria dot fr
2005-07-17 21:22 ` pinskia at gcc dot gnu dot org
2005-07-19  4:17 ` cvs-commit at gcc dot gnu dot org
2005-07-19  4:18 ` pinskia at gcc dot gnu dot org
2005-07-19  4:19 ` pinskia at gcc dot gnu dot org
2005-07-30  8:18 ` hp at gcc dot gnu dot org
2005-08-08 15:05 ` reichelt at gcc dot gnu dot org
2005-08-08 15:08 ` pinskia 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=20050715203958.12251.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).