From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 512FB394FC14; Sun,  9 May 2021 15:43:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 512FB394FC14
From: "lucier at math dot purdue.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100152] [10/11/12 Regression] used caller-saved register
 not preserved across a call.
Date: Sun, 09 May 2021 15:43:35 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.3.0
X-Bugzilla-Keywords: ra, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lucier at math dot purdue.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-100152-4-u1vuqRvtcQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-100152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-100152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 09 May 2021 15:43:36 -0000

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

--- Comment #49 from lucier at math dot purdue.edu ---

> > and "make; make -k check".=20
>=20
> Which, presumably, succeeded [repeatably?] (also presumably with some
> failing tests, since we don't have a clean testsuite on macOS).

It gave reasonable results, the summary is here

https://gcc.gnu.org/pipermail/gcc-testresults/2021-May/691571.html

>=20
> I then applied the patch, configured, "make; make
> > -k check" and the make check always stops with
> >=20
> > <stuff removed>
> > Running
> > /Users/lucier/programs/gcc/gcc-mainline/libstdc++-v3/testsuite/libstdc+=
+-dg/
> > conformance.exp ...
> > WARNING: program timed out.
>=20
> There's not quite enough information here - it would be useful to know wh=
ich
> test(s) timed out - running "make check -jN -k" (where N is some sensible
> number for the cores on your machine) would help since that will then pri=
nt
> which tests timeout.

I had previously tried "make -j20 -k check" and "make -j30 -k check", which
both gave the same "WARNING: program timed out." message, but where, precis=
ely,
it timed out I couldn't tell.  That's why I did it serially, let it run for=
 a
few days, and that's the last thing that printed, immediately after

Running
/Users/lucier/programs/gcc/gcc-mainline/libstdc++-v3/testsuite/libstdc++-dg=
/conformance.exp
...


>=20
> > Sorry, I don't know what's going on.
>=20
> The proposed patch is experimental - I haven't had an opportunity to test=
 it
> across the range of platforms - it might be incomplete or incorrect.=