public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/61325] [4.10 regression] aarch64_be build fails
Date: Mon, 16 Jun 2014 21:40:00 -0000	[thread overview]
Message-ID: <bug-61325-4-oyTIWetMT2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61325-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61325

--- Comment #9 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
Author: vmakarov
Date: Mon Jun 16 21:39:42 2014
New Revision: 211715

URL: https://gcc.gnu.org/viewcvs?rev=211715&root=gcc&view=rev
Log:
2014-06-16  Vladimir Makarov  <vmakarov@redhat.com>

    PR rtl-optimization/61325
    * lra-constraints.c (valid_address_p): Add forward declaration.
    (simplify_operand_subreg): Check address validity before and after
    alter_reg of memory subreg.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/lra-constraints.c


  parent reply	other threads:[~2014-06-16 21:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 22:44 [Bug rtl-optimization/61325] New: " christophe.lyon at st dot com
2014-05-26 22:45 ` [Bug rtl-optimization/61325] " christophe.lyon at st dot com
2014-05-27  7:38 ` rguenth at gcc dot gnu.org
2014-05-29 17:31 ` vmakarov at gcc dot gnu.org
2014-05-29 17:37 ` vmakarov at gcc dot gnu.org
2014-06-02 10:51 ` rguenth at gcc dot gnu.org
2014-06-06 17:22 ` vmakarov at gcc dot gnu.org
2014-06-06 17:23 ` vmakarov at gcc dot gnu.org
2014-06-16 21:40 ` vmakarov at gcc dot gnu.org [this message]
2014-06-16 21:41 ` vmakarov 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-61325-4-oyTIWetMT2@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).