public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mueller 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: Mon, 13 Mar 2006 16:17:00 -0000 [thread overview] Message-ID: <20060313161752.9509.qmail@sourceware.org> (raw) In-Reply-To: <bug-26626-12049@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from mueller at gcc dot gnu dot org 2006-03-13 16:17 ------- it looks to me that this commit exposed/introduced the ICE: r111300 | dberlin | 2006-02-20 14:38:01 +0100 (Mon, 20 Feb 2006) | 22 lines Changed paths: M /trunk/gcc/ChangeLog M /trunk/gcc/passes.c M /trunk/gcc/tree-flow.h M /trunk/gcc/tree-pass.h M /trunk/gcc/tree-sra.c M /trunk/gcc/tree-ssa-alias.c M /trunk/gcc/tree-ssa-forwprop.c M /trunk/gcc/tree-ssa-operands.c M /trunk/gcc/tree.h 2006-02-20 Daniel Berlin <dberlin@dberlin.org> * tree.h (struct tree_memory_tag): Add is_used_alone member. (TMT_USED_ALONE): New macro. * tree-pass.h (PROP_tmt_usage): New property. (TODO_update_tmt_usage): New todo. * tree-ssa-alias.c (updating_used_alone): New variable. (recalculate_used_alone): New function. (compute_may_aliases): Set updating_used_alone, call recalculate_used_alone. * tree-sra.c (pass_sra): Note that this pass destroys PROP_tmt_usage, and add TODO_update_tmt_usage. * tree-ssa-forwprop.c (pass_forwprop): Ditto. * tree-flow.h (updating_used_alone): Prototype. (recalculate_used_alone): Ditto. * passes.c (execute_todo): Add code to set updating_used_alone, and call recalculate. * tree-ssa-operands.c (add_virtual_operand): Only append bare def for clobber if used alone, and add assert to verify used_alone status. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26626
next prev parent reply other threads:[~2006-03-13 16:17 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 2006-03-13 16:17 ` mueller at gcc dot gnu dot org [this message] 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=20060313161752.9509.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).