public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45109] [4.4 Regression] ICE: in get_constraint_for_component_ref, at tree-ssa-structalias.c:2932
Date: Wed, 28 Jul 2010 19:36:00 -0000 [thread overview]
Message-ID: <20100728193630.14970.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45109-19497@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from rguenth at gcc dot gnu dot org 2010-07-28 19:36 -------
Confirmed on x86_64-linux. Not similar to PR44946, but I fixed a similar bug
on the mem-ref branch.
Thus, mine.
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |rguenth at gcc dot gnu dot
|dot org |org
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed|0 |1
GCC target triplet|mipsel-linux-uclibc |mipsel-linux-uclibc, x86_64-
| |*-*
Known to work| |4.3.4
Last reconfirmed|0000-00-00 00:00:00 |2010-07-28 19:36:29
date| |
Summary|ICE: in |[4.4 Regression] ICE: in
|get_constraint_for_component|get_constraint_for_component
|_ref, at tree-ssa- |_ref, at tree-ssa-
|structalias.c:2932 |structalias.c:2932
Target Milestone|--- |4.4.5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45109
next prev parent reply other threads:[~2010-07-28 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 17:08 [Bug tree-optimization/45109] New: " jipeng at broadcom dot com
2010-07-28 17:10 ` [Bug tree-optimization/45109] " jipeng at broadcom dot com
2010-07-28 19:05 ` mikpe at it dot uu dot se
2010-07-28 19:36 ` rguenth at gcc dot gnu dot org [this message]
2010-08-08 15:45 ` [Bug tree-optimization/45109] [4.4 Regression] " rguenth at gcc dot gnu dot org
2010-08-08 15:48 ` rguenth at gcc dot gnu dot org
2010-08-08 15:51 ` rguenth at gcc dot gnu dot org
2010-08-08 15:52 ` rguenth 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=20100728193630.14970.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).