Bug 48565 - libstdc++ testsuite failures when using -pipe
Summary: libstdc++ testsuite failures when using -pipe
Status: UNCONFIRMED
Alias: None
Product: gcc
Classification: Unclassified
Component: testsuite (show other bugs)
Version: 4.6.1
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-12 00:48 UTC by Allan McRae
Modified: 2011-07-10 17:20 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Allan McRae 2011-04-12 00:48:05 UTC
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
Comment 1 Jonathan Wakely 2011-04-12 07:48:36 UTC
Those tests have to use -save-temps to inspect the assembler output, I think the answer is to not use -pipe
Comment 2 Jakub Jelinek 2011-04-12 09:44:47 UTC
Or sed it out of C{XXFLAGS} when determining what flags to pass to the testsuite.
Comment 3 Allan McRae 2011-04-13 10:35:24 UTC
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?
Comment 4 Jonathan Wakely 2011-04-13 15:09:36 UTC
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.
Comment 5 Jonathan Wakely 2011-04-13 15:12:31 UTC
(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