This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
[v3] libstdc++/42491
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Wed, 6 Jan 2010 15:25:31 -0800
- Subject: [v3] libstdc++/42491
This is about running C++0x code in the performance testsuite, namely
<future> type stuff. Well, one solution is to just run all the
performance suite with -gnu=stdc++0x. And since that seems simple
and easy, I did that. At some point in the future we may want to do
dual-runs, or something more elaborate.
This kind of leads us to PR42634, as it now is triggered via 'make
check-performance'. Although not great, it doesn't seem like it's worth
waiting for that to be fixed before this goes in.
tested x86/linux
-benjamin
2010-01-06 Benjamin Kosnik <bkoz@redhat.com>
PR libstdc++/42491
* scripts/check_performance (CXX): Add -std=gnu++0x.
* testsuite/performance/30_threads/future/polling.cc: Mark up as
using threads.
Index: scripts/check_performance
===================================================================
--- scripts/check_performance (revision 155680)
+++ scripts/check_performance (working copy)
@@ -32,7 +32,7 @@
-Wl,--rpath -Wl,$BUILD_DIR/src/.libs"
ST_FLAG="-static"
LINK=$SH_FLAG
-CXX="$COMPILER $INCLUDES $FLAGS $CXXFLAGS $LINK"
+CXX="$COMPILER $INCLUDES $FLAGS -std=gnu++0x $CXXFLAGS $LINK"
LIBS="./libtestc++.a"
TESTS_FILE="testsuite_files_performance"
Index: testsuite/performance/30_threads/future/polling.cc
===================================================================
--- testsuite/performance/30_threads/future/polling.cc (revision 155680)
+++ testsuite/performance/30_threads/future/polling.cc (working copy)
@@ -28,6 +28,10 @@
int main()
{
+#ifdef TEST_T1
+#define thread_type true
+#endif
+
using namespace __gnu_test;
time_counter time;
resource_counter resource;