public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/48565] New: libstdc++ testsuite failures when using -pipe
@ 2011-04-12 0:48 allan at archlinux dot org
2011-04-12 7:48 ` [Bug testsuite/48565] " redi at gcc dot gnu.org
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: allan at archlinux dot org @ 2011-04-12 0:48 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
Summary: libstdc++ testsuite failures when using -pipe
Product: gcc
Version: 4.6.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: allan@archlinux.org
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
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug testsuite/48565] libstdc++ testsuite failures when using -pipe
2011-04-12 0:48 [Bug testsuite/48565] New: libstdc++ testsuite failures when using -pipe allan at archlinux dot org
@ 2011-04-12 7:48 ` redi at gcc dot gnu.org
2011-04-12 9:45 ` jakub at gcc dot gnu.org
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2011-04-12 7:48 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 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
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug testsuite/48565] libstdc++ testsuite failures when using -pipe
2011-04-12 0:48 [Bug testsuite/48565] New: libstdc++ testsuite failures when using -pipe allan at archlinux dot org
2011-04-12 7:48 ` [Bug testsuite/48565] " redi at gcc dot gnu.org
@ 2011-04-12 9:45 ` jakub at gcc dot gnu.org
2011-04-13 10:35 ` allan at archlinux dot org
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: jakub at gcc dot gnu.org @ 2011-04-12 9:45 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-04-12 09:44:47 UTC ---
Or sed it out of C{XXFLAGS} when determining what flags to pass to the
testsuite.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug testsuite/48565] libstdc++ testsuite failures when using -pipe
2011-04-12 0:48 [Bug testsuite/48565] New: libstdc++ testsuite failures when using -pipe allan at archlinux dot org
2011-04-12 7:48 ` [Bug testsuite/48565] " redi at gcc dot gnu.org
2011-04-12 9:45 ` jakub at gcc dot gnu.org
@ 2011-04-13 10:35 ` allan at archlinux dot org
2011-04-13 15:10 ` redi at gcc dot gnu.org
2011-04-13 15:13 ` redi at gcc dot gnu.org
4 siblings, 0 replies; 6+ messages in thread
From: allan at archlinux dot org @ 2011-04-13 10:35 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
--- Comment #3 from Allan McRae <allan at archlinux dot org> 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?
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/48565] libstdc++ testsuite failures when using -pipe
2011-04-12 0:48 [Bug testsuite/48565] New: libstdc++ testsuite failures when using -pipe allan at archlinux dot org
` (2 preceding siblings ...)
2011-04-13 10:35 ` allan at archlinux dot org
@ 2011-04-13 15:10 ` redi at gcc dot gnu.org
2011-04-13 15:13 ` redi at gcc dot gnu.org
4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2011-04-13 15:10 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 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.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug testsuite/48565] libstdc++ testsuite failures when using -pipe
2011-04-12 0:48 [Bug testsuite/48565] New: libstdc++ testsuite failures when using -pipe allan at archlinux dot org
` (3 preceding siblings ...)
2011-04-13 15:10 ` redi at gcc dot gnu.org
@ 2011-04-13 15:13 ` redi at gcc dot gnu.org
4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2011-04-13 15:13 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-04-13 15:13 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-04-12 0:48 [Bug testsuite/48565] New: libstdc++ testsuite failures when using -pipe allan at archlinux dot org
2011-04-12 7:48 ` [Bug testsuite/48565] " redi at gcc dot gnu.org
2011-04-12 9:45 ` jakub at gcc dot gnu.org
2011-04-13 10:35 ` allan at archlinux dot org
2011-04-13 15:10 ` redi at gcc dot gnu.org
2011-04-13 15:13 ` redi at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).