public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/49712] internal compiler error: in gen_lsm_tmp_name, at tree-ssa-loop-im.c:2048
Date: Tue, 12 Jul 2011 08:51:00 -0000 [thread overview]
Message-ID: <bug-49712-4-Jf1Jj0JDHn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49712-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49712
--- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-07-12 08:48:45 UTC ---
(In reply to comment #3)
> Created attachment 24742 [details]
> gcc47-pr49712.patch
>
> Untested fix.
>
> Wonder if TARGET_MEM_REF shouldn't be handled alongside MEM_REF in
> ref_always_accessed_p too.
Looks obvious.
next prev parent reply other threads:[~2011-07-12 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 5:03 [Bug c/49712] New: " regehr at cs dot utah.edu
2011-07-12 5:16 ` [Bug tree-optimization/49712] " pinskia at gcc dot gnu.org
2011-07-12 6:38 ` jakub at gcc dot gnu.org
2011-07-12 7:03 ` jakub at gcc dot gnu.org
2011-07-12 8:51 ` rguenth at gcc dot gnu.org [this message]
2011-07-12 8:54 ` rguenth at gcc dot gnu.org
2011-07-12 9:13 ` jakub at gcc dot gnu.org
2011-08-04 15:19 ` jakub 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-49712-4-Jf1Jj0JDHn@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).