public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/48493] [ICE] [ARM] in expand_expr_addr_expr_1, at expr.c
Date: Tue, 21 Jun 2011 09:06:00 -0000 [thread overview]
Message-ID: <bug-48493-4-5FOCuqkDOW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48493-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48493
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpe at it dot uu.se,
| |rguenth at gcc dot gnu.org
--- Comment #4 from Mikael Pettersson <mikpe at it dot uu.se> 2011-06-21 09:04:00 UTC ---
It's triggered by the big MEM-REF merge in r161655:
Author: rguenth
Date: Thu Jul 1 08:49:19 2010
New Revision: 161655
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=161655
Log:
2010-07-01 Richard Guenther <rguenther@suse.de>
PR middle-end/42834
PR middle-end/44468
* doc/gimple.texi (is_gimple_mem_ref_addr): Document.
* doc/generic.texi (References to storage): Document MEM_REF.
* tree-pretty-print.c (dump_generic_node): Handle MEM_REF.
...
next prev parent reply other threads:[~2011-06-21 9:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 13:15 [Bug middle-end/48493] New: [ICE] " yufeng at gcc dot gnu.org
2011-05-06 11:09 ` [Bug middle-end/48493] [ICE] [ARM] " ramana at gcc dot gnu.org
2011-05-06 11:27 ` ramana at gcc dot gnu.org
2011-05-17 22:38 ` michael.hope at linaro dot org
2011-06-21 9:06 ` mikpe at it dot uu.se [this message]
2011-06-21 10:46 ` rguenth at gcc dot gnu.org
2011-06-21 11:25 ` mikpe at it dot uu.se
2011-06-21 11:41 ` rguenther at suse dot de
2011-06-24 10:00 ` mikpe at it dot uu.se
2012-05-05 0:14 ` [Bug middle-end/48493] [4.6/4.7/4.8 Regression] ice in expand_expr_addr_expr_1 with complex types and mem_ref pinskia at gcc dot gnu.org
2012-05-05 0:15 ` pinskia at gcc dot gnu.org
2012-05-29 14:08 ` rguenth at gcc dot gnu.org
2012-05-29 14:08 ` rguenth at gcc dot gnu.org
2012-05-30 12:47 ` [Bug middle-end/48493] [4.6/4.7 " rguenth at gcc dot gnu.org
2012-05-30 17:23 ` pinskia at gcc dot gnu.org
2012-05-30 19:14 ` pinskia at gcc dot gnu.org
2012-05-31 7:37 ` mikpe at it dot uu.se
2012-05-31 11:07 ` rguenth at gcc dot gnu.org
2012-05-31 11:08 ` rguenth at gcc dot gnu.org
2012-05-31 11:08 ` [Bug middle-end/48493] [4.6 " rguenth at gcc dot gnu.org
2012-05-31 11:13 ` rguenth at gcc dot gnu.org
2013-04-12 16:25 ` 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-48493-4-5FOCuqkDOW@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).