[Bug target/79912] [7/8 regression] LRA unable to generate reloads after r245655

[Bug target/79912] [7/8 regression] LRA unable to generate reloads after r245655

[palmer at dabbelt dot com]

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

Palmer Dabbelt <palmer at dabbelt dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #21 from Palmer Dabbelt <palmer at dabbelt dot com> ---
(In reply to mpf from comment #20)
> Palmer: There is a commit listed for this bug, did that fix the issue and
> can the bug be marked fixed?

The actual regression is fixed but there's some cleanup left to do.  I guess I
was hoping to get to it 6 month ago but I didn't.  I'm going to mark this as
"RESOLVED FIXED" (I'm new to Bugzilla, so sorry if that's the wrong way to do
it), we'll just try to remember to clean it up eventually.
>From gcc-bugs-return-572159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Aug 15 16:28:23 2017
Return-Path: <gcc-bugs-return-572159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130430 invoked by alias); 15 Aug 2017 16:28:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129934 invoked by uid 89); 15 Aug 2017 16:27:52 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=Hx-languages-length:696, UD:msg01303.html, msg01303html, Strangely
X-Spam-User: qpsmtpd, 2 recipients
X-HELO: relay1.mentorg.com
Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 15 Aug 2017 16:27:50 +0000
Received: from nat-ies.mentorg.com ([192.94.31.2] helo=svr-ies-mbx-01.mgc.mentorg.com)	by relay1.mentorg.com with esmtp 	id 1dheh2-0004ns-AE from joseph_myers@mentor.com ; Tue, 15 Aug 2017 09:27:48 -0700
Received: from digraph.polyomino.org.uk (137.202.0.87) by svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 15 Aug 2017 17:27:45 +0100
Received: from jsm28 (helo=localhost)	by digraph.polyomino.org.uk with local-esmtp (Exim 4.86_2)	(envelope-from <joseph@codesourcery.com>)	id 1dhegv-0003fl-OT; Tue, 15 Aug 2017 16:27:41 +0000
Date: Tue, 15 Aug 2017 19:44:00 -0000
From: Joseph Myers <joseph@codesourcery.com>
To: Martin Sebor <msebor@gmail.com>
CC: Jonathan Wakely <jwakely.gcc@gmail.com>, Eric Gallager	<egall@gwmail.gwu.edu>, <gcc-bugs@gcc.gnu.org>, GCC Mailing List	<gcc@gcc.gnu.org>
Subject: Re: [Bug web/?????] New: Fwd: failure notice: Bugzilla down.
In-Reply-To: <2415bb8f-26cc-17b7-11a2-4012e1dab9c4@gmail.com>
Message-ID: <alpine.DEB.2.20.1708151626150.12690@digraph.polyomino.org.uk>
References: <CAMfHzOsXnceTY=YHFfC_qDPYYgkyer=dm5ESABuO_KjuQ60MXw@mail.gmail.com> <67267f8d-030b-e5ac-21b1-8d5c6911045d@gmail.com> <CAH6eHdTsKsdnXG-edvWWHh-Vd45jKuiMxL8V3W34+j+86aFmHA@mail.gmail.com> <2415bb8f-26cc-17b7-11a2-4012e1dab9c4@gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1)
X-SW-Source: 2017-08/txt/msg01718.txt.bz2
Content-length: 646

On Tue, 15 Aug 2017, Martin Sebor wrote:

> It looks like the data loss extends beyond 8/14.  Bug 81840
> was created Sunday afternoon but is not in the database:
>
>   https://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01303.html
>
> (Strangely, 81841 is there, as is 81839.)

That's another 81839 replacing the original 81839.  As I noted on
overseers, the cut-off for GCC Bugzilla appears to be between
<https://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01289.html> and
<https://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01290.html>, early Sunday
morning UTC (and for sourceware Bugzilla it may well be similar).

--
Joseph S. Myers
joseph@codesourcery.com