From: Hans-Peter Nilsson <hp@axis.com>
To: <jwakely@redhat.com>
Cc: <libstdc++@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>
Subject: Splitting up 27_io/basic_istream/ignore/wchar_t/94749.cc (takes too long)
Date: Fri, 9 Jun 2023 18:20:26 +0200 [thread overview]
Message-ID: <20230609162026.CC34320433@pchp3.se.axis.com> (raw)
Hi!
The test 27_io/basic_istream/ignore/wchar_t/94749.cc takes
about 10 minutes to run for cris-elf in the "gdb simulator"
here on my arguably way-past-retirement machine (and it
looks like it gained a minute with LRA). I've seen it
timing out every now and then on busy days with load >
`nproc`. Usually it happens some time after I've forgot
about why. :)
It has had some performance surgery before (pruning for
simulators, doubling timeout for ilp32). I'd probably just
try cutting along the function boundaries and keep those
parts separate that have >1 min execution time.
Anyway, your thoughts on the matter would be appreciated.
brgds, H-P
next reply other threads:[~2023-06-09 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 16:20 Hans-Peter Nilsson [this message]
2023-06-09 17:18 ` Mike Stump
2023-06-09 17:49 ` Hans-Peter Nilsson
2023-06-09 21:47 ` Bernhard Reutner-Fischer
2023-06-10 18:29 ` Mike Stump
2023-06-12 8:35 ` Bernhard Reutner-Fischer
2023-06-12 22:26 ` Mike Stump
2023-06-09 20:40 ` Jonathan Wakely
2023-06-10 4:05 ` [PATCH] (Re: Splitting up 27_io/basic_istream/ignore/wchar_t/94749.cc (takes too long)) Hans-Peter Nilsson
2023-06-10 7:12 ` Jonathan Wakely
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=20230609162026.CC34320433@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@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).