On 09/10/20 14:02 +0100, Jonathan Wakely wrote:
It looks like our check-performance target runs completely unoptimized,
which is a bit silly. This exports the CXXFLAGS from the parent make
process to the check_performance script.
libstdc++-v3/ChangeLog:
* scripts/check_performance: Use gnu++11 instead of gnu++0x.
* testsuite/Makefile.am (check-performance): Export CXXFLAGS to
child process.
* testsuite/Makefile.in: Regenerate.
A small adjustment to that last patch.
Tested powerpc64le-linux. Committed to trunk.
commit 6ce2cb116af6e0965ff0dd69e7fd1925cf5dc68c
Author: Jonathan Wakely <jwak...@redhat.com>
Date: Fri Oct 9 14:07:22 2020
libstdc++: Adjust variable export in makefile
We usually export variables in recipes this way. I'm not sure it's
necessary, but it's consistent.
libstdc++-v3/ChangeLog:
* testsuite/Makefile.am: Set and export variable separately.
* testsuite/Makefile.in: Regenerate.
diff --git a/libstdc++-v3/testsuite/Makefile.am b/libstdc++-v3/testsuite/Makefile.am
index 2fca179fca4..7b412411bfe 100644
--- a/libstdc++-v3/testsuite/Makefile.am
+++ b/libstdc++-v3/testsuite/Makefile.am
@@ -182,7 +182,7 @@ check-compile: testsuite_files ${compile_script}
check_performance_script=${glibcxx_srcdir}/scripts/check_performance
check-performance: testsuite_files_performance ${performance_script}
-@(chmod + ${check_performance_script}; \
- export CXXFLAGS="$(CXXFLAGS)"; \
+ CXXFLAGS='$(CXXFLAGS)'; export CXXFLAGS; \
${check_performance_script} ${glibcxx_srcdir} ${glibcxx_builddir})
# Runs the testsuite in debug mode.
