public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49742] [4.7 Regression] ICE for gcc.dg/vect/O3-pr39675-2.c on ARM
Date: Tue, 19 Jul 2011 09:37:00 -0000 [thread overview]
Message-ID: <bug-49742-4-btw14fncKP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49742-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49742
rsandifo@gcc.gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |rsandifo at gcc dot gnu.org
|gnu.org |
--- Comment #6 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> 2011-07-19 09:35:46 UTC ---
(In reply to comment #4)
> Predictive commoning appears to be doing this.
>
> RichardS: you mentioned something about looking at a predictive commoning
> issue. Does this ring a bell ?
Yeah, it is indeed the same thing. Handling gimple_call_lhs_ptr in
get_references_in_stmt seems to fix it. I'm testing a patch now.
Richard
next prev parent reply other threads:[~2011-07-19 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 1:07 [Bug tree-optimization/49742] New: " janis at gcc dot gnu.org
2011-07-14 9:13 ` [Bug target/49742] [4.7 Regression] " rguenth at gcc dot gnu.org
2011-07-14 23:44 ` ramana at gcc dot gnu.org
2011-07-15 0:18 ` ramana at gcc dot gnu.org
2011-07-15 0:23 ` ramana at gcc dot gnu.org
2011-07-18 8:24 ` rguenth at gcc dot gnu.org
2011-07-19 9:37 ` rsandifo at gcc dot gnu.org [this message]
2011-07-19 12:43 ` rsandifo at gcc dot gnu.org
2011-07-19 12:46 ` [Bug tree-optimization/49742] " rsandifo at gcc dot gnu.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=bug-49742-4-btw14fncKP@http.gcc.gnu.org/bugzilla/ \
--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).