public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <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 19:22:04 +0000 [thread overview]
Message-ID: <bug-100152-4-0upJcty7Wf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100152-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100152
--- Comment #50 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to lucier from comment #49)
> > > Running
> > > /Users/lucier/programs/gcc/gcc-mainline/libstdc++-v3/testsuite/libstdc++-dg/
> > > conformance.exp ...
> > > WARNING: program timed out.
> >
> > There's not quite enough information here - it would be useful to know which
> > 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 print
> > 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,
> precisely, 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 ...
hmm, there was a modification made to the testsuite output that relates
timeouts to the test that failed. However there are buggy versions of expect
on some darwin versions, which might well defeat that. I have a patched
version of expect which I use in conjunction with dejagnu 1.6.2 and
tcl-8.6(.9).
If you look at x86_64-apple-darwin19/libstdc++/testsuite/libstdc++.log, then
perhaps you can see the last test that was run in the serialised case.
FWIW I see some timeout fails with unpatched master on x86_64-darwin19 (on two
systems, one with corei5 and one with xeon w) - threads/barrier and randomly
threads/latch. There are some known limitations with the implementations there
that are planned to be addressed in GCC12.
next prev parent reply other threads:[~2021-05-09 19:22 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 13:48 [Bug target/100152] New: Possible 10.3 bad code generation regression from 10.2/9.3 on Mac OS 10.15.7 (Catalina) lucier at math dot purdue.edu
2021-04-20 13:48 ` [Bug target/100152] " lucier at math dot purdue.edu
2021-04-20 13:50 ` lucier at math dot purdue.edu
2021-04-20 14:33 ` iains at gcc dot gnu.org
2021-04-20 14:36 ` iains at gcc dot gnu.org
2021-04-20 14:40 ` lucier at math dot purdue.edu
2021-04-20 14:43 ` iains at gcc dot gnu.org
2021-04-20 14:58 ` lucier at math dot purdue.edu
2021-04-20 15:02 ` iains at gcc dot gnu.org
2021-04-20 15:09 ` lucier at math dot purdue.edu
2021-04-20 15:13 ` lucier at math dot purdue.edu
2021-04-20 15:17 ` iains at gcc dot gnu.org
2021-04-20 15:24 ` lucier at math dot purdue.edu
2021-04-20 17:22 ` lucier at math dot purdue.edu
2021-04-21 4:27 ` gabravier at gmail dot com
2021-04-21 8:52 ` iains at gcc dot gnu.org
2021-04-21 13:17 ` lucier at math dot purdue.edu
2021-04-21 15:32 ` iains at gcc dot gnu.org
2021-04-21 18:12 ` lucier at math dot purdue.edu
2021-04-21 18:18 ` iains at gcc dot gnu.org
2021-04-21 18:29 ` iains at gcc dot gnu.org
2021-04-21 20:00 ` iains at gcc dot gnu.org
2021-04-21 20:38 ` iains at gcc dot gnu.org
2021-04-21 23:24 ` lucier at math dot purdue.edu
2021-04-22 10:28 ` [Bug target/100152] [10.3, 11, 12 Regression] [Darwin, X86] used caller-saved register not preserved across a call iains at gcc dot gnu.org
2021-04-22 12:54 ` lucier at math dot purdue.edu
2021-04-22 14:35 ` feeley at iro dot umontreal.ca
2021-04-22 23:13 ` [Bug target/100152] [10.3, 11, 12 Regression] " iains at gcc dot gnu.org
2021-04-23 0:32 ` iains at gcc dot gnu.org
2021-04-23 6:51 ` iains at gcc dot gnu.org
2021-04-23 8:13 ` [Bug target/100152] [10/11/12 " rguenth at gcc dot gnu.org
2021-04-23 8:32 ` iains at gcc dot gnu.org
2021-04-23 8:48 ` iains at gcc dot gnu.org
2021-04-23 8:54 ` rguenth at gcc dot gnu.org
2021-04-23 8:58 ` rguenth at gcc dot gnu.org
2021-04-23 9:05 ` rguenth at gcc dot gnu.org
2021-04-23 9:09 ` iains at gcc dot gnu.org
2021-04-23 11:02 ` rguenth at gcc dot gnu.org
2021-04-23 12:34 ` iains at gcc dot gnu.org
2021-04-23 12:57 ` rguenth at gcc dot gnu.org
2021-04-23 12:58 ` rguenth at gcc dot gnu.org
2021-04-23 13:13 ` iains at gcc dot gnu.org
2021-04-24 12:41 ` iains at gcc dot gnu.org
2021-04-24 12:45 ` cvs-commit at gcc dot gnu.org
2021-04-24 18:45 ` iains at gcc dot gnu.org
2021-05-02 15:36 ` iains at gcc dot gnu.org
2021-05-03 7:54 ` iains at gcc dot gnu.org
2021-05-09 1:57 ` lucier at math dot purdue.edu
2021-05-09 7:25 ` iains at gcc dot gnu.org
2021-05-09 15:43 ` lucier at math dot purdue.edu
2021-05-09 19:22 ` iains at gcc dot gnu.org [this message]
2021-05-09 20:00 ` lucier at math dot purdue.edu
2021-05-09 22:36 ` iains at gcc dot gnu.org
2021-05-11 7:48 ` iains at gcc dot gnu.org
2021-05-13 3:35 ` lucier at math dot purdue.edu
2021-05-14 14:04 ` jakub at gcc dot gnu.org
2021-07-09 16:42 ` cvs-commit at gcc dot gnu.org
2021-07-20 6:52 ` cvs-commit at gcc dot gnu.org
2021-07-20 7:00 ` [Bug target/100152] [10 " iains at gcc dot gnu.org
2021-07-22 15:21 ` lucier at math dot purdue.edu
2022-05-29 19:13 ` cvs-commit at gcc dot gnu.org
2022-05-29 19:25 ` iains 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-100152-4-0upJcty7Wf@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).