Tested powerpc64le-linux, pushed to trunk.
This test spawns thousands of threads and so times out if the tests are
run with a low timeout value and the machine is busy.
libstdc++-v3/ChangeLog:
* testsuite/ext/rope/pthread7-rope.cc: Add dg-timeout-factor.
---
libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc
b/libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc
index 9a870d1fc2e..b0b92adcfa9 100644
--- a/libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc
+++ b/libstdc++-v3/testsuite/ext/rope/pthread7-rope.cc
@@ -20,6 +20,7 @@
// { dg-do run }
// { dg-options "-pthread" }
// { dg-require-effective-target pthread }
+// { dg-timeout-factor 2 }
#include <ext/rope>
#include <cstring>
@@ -33,7 +34,7 @@ typedef __gnu_cxx::rope<char, std::allocator<char> >
rope_type;
rope_type foo2;
rope_type foo4;
-void* thread_main(void *)
+void* thread_main(void *)
{
// To see a problem with gcc 3.3 and before, set a break point here.
// Single step through c_str implementation, call sched_yield after
--
2.31.1
