public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/57134] ICE with -mstrict-align and inline assembly on ppc64
Date: Wed, 01 May 2013 14:32:00 -0000	[thread overview]
Message-ID: <bug-57134-4-7y3AhkeTdE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57134-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57134

Alan Modra <amodra at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-05-01
                 CC|                            |amodra at gmail dot com
     Ever Confirmed|0                           |1

--- Comment #1 from Alan Modra <amodra at gmail dot com> 2013-05-01 14:32:49 UTC ---
I think the bug here is that we lose EXPAND_MEMORY when recursively calling
expand_expr() for the inner part of a COMPONENT_REF.


  reply	other threads:[~2013-05-01 14:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 12:16 [Bug middle-end/57134] New: " anton at samba dot org
2013-05-01 14:32 ` amodra at gmail dot com [this message]
2013-05-02  8:06 ` [Bug middle-end/57134] [4.9 Regression] " rguenth at gcc dot gnu.org
2013-06-12  9:29 ` amodra at gmail dot com
2013-08-04 12:32 ` anton at samba dot org
2013-09-16 13:20 ` jamborm at gcc dot gnu.org
2013-09-16 13:49 ` amodra at gmail dot com
2013-09-24 11:32 ` amodra at gcc dot gnu.org
2013-09-24 11:33 ` amodra at gmail dot com

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-57134-4-7y3AhkeTdE@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).