public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/56791] [4.8/4.9 Regression] Segmentation fault in stage2 gengenrtl -- Incorrect instruction sequence generated by reload
Date: Thu, 16 Jan 2014 20:52:00 -0000	[thread overview]
Message-ID: <bug-56791-4-2MmDVO1zJe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56791-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Author: law
Date: Thu Jan 16 20:51:24 2014
New Revision: 206688

URL: http://gcc.gnu.org/viewcvs?rev=206688&root=gcc&view=rev
Log:
014-01-16  Bernd Schmidt  <bernds@codesourcery.com>

        PR middle-end/56791
        * reload.c (find_reloads_address_1): Do not use RELOAD_OTHER
        * when
        pushing a reload for an autoinc when we had previously reloaded an
        inner part of the address.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/reload.c


      parent reply	other threads:[~2014-01-16 20:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-31  0:58 [Bug middle-end/56791] New: " danglin at gcc dot gnu.org
2013-04-02  9:11 ` [Bug middle-end/56791] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2013-04-09 23:17 ` danglin at gcc dot gnu.org
2013-05-31 10:58 ` jakub at gcc dot gnu.org
2013-07-28 18:52 ` danglin at gcc dot gnu.org
2013-09-21  0:00 ` danglin at gcc dot gnu.org
2013-10-16  9:48 ` jakub at gcc dot gnu.org
2013-10-16 19:00 ` bernds at gcc dot gnu.org
2013-10-16 19:18 ` dave.anglin at bell dot net
2013-11-22 10:44 ` rguenth at gcc dot gnu.org
2013-12-31 18:08 ` danglin at gcc dot gnu.org
2014-01-03 12:46 ` bernds at gcc dot gnu.org
2014-01-03 15:52 ` dave.anglin at bell dot net
2014-01-07 20:47 ` law at redhat dot com
2014-01-16 20:52 ` law at redhat dot com
2014-01-16 20:52 ` law at gcc dot gnu.org [this message]

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-56791-4-2MmDVO1zJe@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).