public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dberlin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/27341] [4.2 Regression] ICE in in add_virtual_operand with complex types Date: Thu, 15 Jun 2006 15:18:00 -0000 [thread overview] Message-ID: <20060615150444.18381.qmail@sourceware.org> (raw) In-Reply-To: <bug-27341-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from dberlin at gcc dot gnu dot org 2006-06-15 15:04 ------- This should fix it It looks like gimplify_val never calls mark_new_vars_to_rename, but may create new statements that nothing else gets a handle to. Index: tree-cfg.c =================================================================== --- tree-cfg.c (revision 114136) +++ tree-cfg.c (working copy) @@ -5584,6 +5584,8 @@ gimplify_val (block_stmt_iterator *bsi, TREE_BLOCK (new_stmt) = TREE_BLOCK (orig_stmt); bsi_insert_before (bsi, new_stmt, BSI_SAME_STMT); + if (in_ssa_p) + mark_new_vars_to_rename (new_stmt); return t; } I'll look at this bug anyway -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27341
next prev parent reply other threads:[~2006-06-15 15:04 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-04-27 19:10 [Bug tree-optimization/27341] New: " pinskia at gcc dot gnu dot org 2006-04-27 19:10 ` [Bug tree-optimization/27341] " pinskia at gcc dot gnu dot org 2006-04-27 19:11 ` pinskia at gcc dot gnu dot org 2006-04-27 19:14 ` pinskia at gcc dot gnu dot org 2006-04-27 19:17 ` pinskia at gcc dot gnu dot org 2006-05-02 7:26 ` pinskia at gcc dot gnu dot org 2006-05-11 8:56 ` rguenth at gcc dot gnu dot org 2006-06-01 3:47 ` pinskia at gcc dot gnu dot org 2006-06-01 3:47 ` pinskia at gcc dot gnu dot org 2006-06-01 12:22 ` dberlin at gcc dot gnu dot org 2006-06-04 18:39 ` mmitchel at gcc dot gnu dot org 2006-06-15 14:35 ` fxcoudert at gcc dot gnu dot org 2006-06-15 14:52 ` dberlin at gcc dot gnu dot org 2006-06-15 15:18 ` dberlin at gcc dot gnu dot org [this message] 2006-06-15 15:20 ` dberlin at dberlin dot org 2006-06-19 14:34 ` dberlin at gcc dot gnu dot org 2006-06-19 14:39 ` dberlin 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=20060615150444.18381.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).