public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/16461] ICE: expected ssa_name, have integer_cst in independent_of_stmt_p, at tree-tailcall.c:210 Date: Fri, 09 Jul 2004 21:21:00 -0000 [thread overview] Message-ID: <20040709212104.23326.qmail@sourceware.org> (raw) In-Reply-To: <20040709210136.16461.falk@debian.org> ------- Additional Comments From dnovillo at gcc dot gnu dot org 2004-07-09 21:21 ------- Confirmed. The bug is in tree-tailcall.c:independent_of_stmt_p. The loop that looks up PHI arguments, ought to handle gimple_min_invariants it finds in PHI operands. It should not assume that they are all SSA_NAMEs. Not quite sure what the right to do is here. We are analyzing ret_1 in statement T.2_6 = ret_1 + ret2_2; and abort as soon as we get to the first operand of # ret_1 = PHI <0(2), ret_11(1)>; Jeff, IIRC you implemented this. -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |law at gcc dot gnu dot org |dot org | Status|UNCONFIRMED |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16461
next prev parent reply other threads:[~2004-07-09 21:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-09 21:01 [Bug tree-optimization/16461] New: " falk at debian dot org 2004-07-09 21:21 ` dnovillo at gcc dot gnu dot org [this message] 2004-07-09 22:15 ` [Bug tree-optimization/16461] [3.5 Regression] " pinskia at gcc dot gnu dot org 2004-07-10 4:56 ` rakdver at gcc dot gnu dot org 2004-07-11 20:02 ` rakdver at gcc dot gnu dot org 2004-07-13 1:03 ` cvs-commit at gcc dot gnu dot org 2004-07-13 1:05 ` rakdver at gcc dot gnu dot org 2004-08-08 23:17 ` cvs-commit 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=20040709212104.23326.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: linkBe 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).