public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-6934] libstdc++ testsuite: Don't run lwg3464.cc tests on simulators Date: Sun, 30 Jan 2022 16:52:33 +0000 (GMT) [thread overview] Message-ID: <20220130165233.1516F3858404@sourceware.org> (raw) https://gcc.gnu.org/g:baf98320ac6cd56da0c0b460fb94e3b87a79220d commit r12-6934-gbaf98320ac6cd56da0c0b460fb94e3b87a79220d Author: Hans-Peter Nilsson <hp@axis.com> Date: Sun Jan 30 02:01:12 2022 +0100 libstdc++ testsuite: Don't run lwg3464.cc tests on simulators These tests have always been failing for my autotester running a cris-elf simulator; when unrestrained they take about 20 minutes each, compared to the (doubled) timeout of 720 seconds, of a total 2h40min for the whole of the libstdc++-v3 testsuite. The tests cover counter overflow and are already disabled for LP64 targets. * testsuite/27_io/basic_istream/get/char/lwg3464.cc: Don't run on simulator targets. * testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc: Likewise. Diff: --- libstdc++-v3/testsuite/27_io/basic_istream/get/char/lwg3464.cc | 2 +- libstdc++-v3/testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/libstdc++-v3/testsuite/27_io/basic_istream/get/char/lwg3464.cc b/libstdc++-v3/testsuite/27_io/basic_istream/get/char/lwg3464.cc index f426ff7dd86..5d4de3d6cb5 100644 --- a/libstdc++-v3/testsuite/27_io/basic_istream/get/char/lwg3464.cc +++ b/libstdc++-v3/testsuite/27_io/basic_istream/get/char/lwg3464.cc @@ -15,7 +15,7 @@ // with this library; see the file COPYING3. If not see // <http://www.gnu.org/licenses/>. -// { dg-do run { target { ! lp64 } } } +// { dg-do run { target { { ! lp64 } && { ! simulator } } } } // { dg-timeout-factor 2 } #include <istream> diff --git a/libstdc++-v3/testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc b/libstdc++-v3/testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc index 4be6beb2310..e2349df8c7d 100644 --- a/libstdc++-v3/testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc +++ b/libstdc++-v3/testsuite/27_io/basic_istream/get/wchar_t/lwg3464.cc @@ -15,7 +15,7 @@ // with this library; see the file COPYING3. If not see // <http://www.gnu.org/licenses/>. -// { dg-do run { target { ! lp64 } } } +// { dg-do run { target { { ! lp64 } && { ! simulator } } } } // { dg-timeout-factor 2 } #include <istream>
reply other threads:[~2022-01-30 16:52 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220130165233.1516F3858404@sourceware.org \ --to=hp@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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: linkBe 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).