When building gcc with "-pipe" in the C{XX}FLAGS, the following test suite failures occur: FAIL: 20_util/enable_shared_from_this/cons/constexpr.cc (test for excess errors) FAIL: 20_util/shared_ptr/cons/constexpr.cc (test for excess errors) FAIL: 20_util/unique_ptr/cons/constexpr.cc (test for excess errors) FAIL: 20_util/weak_ptr/cons/constexpr.cc (test for excess errors) FAIL: 30_threads/future/cons/constexpr.cc (test for excess errors) FAIL: 30_threads/shared_future/cons/constexpr.cc (test for excess errors) This is because the following warning gets outputed: g++: warning: -pipe ignored because -save-temps specified
Those tests have to use -save-temps to inspect the assembler output, I think the answer is to not use -pipe
Or sed it out of C{XXFLAGS} when determining what flags to pass to the testsuite.
So, just to clarify... Is this being seen as something that the person building the gcc test-suite should deal with or something that should be dealt with in the test-suite?
It shouldn't happen unless the person running the testsuite specifies it, so they can not specify it. How did you configure the library to hit this problem? Jakub's suggestion is that the testsuite could filter it out, so that even when users do specify it, the testsuite doesn't use it.
(In reply to comment #4) > How did you configure the library to hit this > problem? I know you said with -pipe in your CFLAGS, is that all? You could probably edit scripts/testsuite_flags to remove -pipe as a workaround