Just simulating a 32 bit CPU, these test take about a minute, and
simulating a 16 bit target with size-optimized multi-word divide /
modulus functions, it takes way too long, so I made the tests not
run on targets without int32plus unless run_expensive_test is true.
Even for a simulated 32 bit target, depending on what machine the test
ends up running on and what the other tests were doing,
std/time/year_month_day/3.cc occaisonally timed out, so I bumped up the
timeout factor a bit.Reduce time/year_month_day/[34].cc timeouts.
2024-08-09 Joern Rennecke <joern.renne...@riscy-ip.com>
libstdc++-v3/
* testsuite/std/time/year_month_day/4.cc:
[!int32plus]: Require run_expensive_tests.
* testsuite/std/time/year_month_day/3.cc: Likewise.
Add // { dg-timeout-factor 1.5 }
Index: std/time/year_month_day/3.cc
===================================================================
--- std/time/year_month_day/3.cc (revision 6614)
+++ std/time/year_month_day/3.cc (working copy)
@@ -1,4 +1,7 @@
// { dg-do run { target c++20 } }
+// Technically, 16 bit targets can run the test, but it takes too long.
+// { dg-require-effective-target run_expensive_tests { target { ! int32plus }
} }
+// { dg-timeout-factor 1.5 }
// Copyright (C) 2021-2024 Free Software Foundation, Inc.
//
Index: std/time/year_month_day/4.cc
===================================================================
--- std/time/year_month_day/4.cc (revision 6614)
+++ std/time/year_month_day/4.cc (working copy)
@@ -1,4 +1,6 @@
// { dg-do run { target c++20 } }
+// Technically, 16 bit targets can run the test, but it takes too long.
+// { dg-require-effective-target run_expensive_tests { target { ! int32plus }
} }
// Copyright (C) 2021-2024 Free Software Foundation, Inc.
//
