This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/54865] New: [parallel mode] tests timeout on power64
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 09 Oct 2012 08:40:31 +0000
- Subject: [Bug libstdc++/54865] New: [parallel mode] tests timeout on power64
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54865
Bug #: 54865
Summary: [parallel mode] tests timeout on power64
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: redi@gcc.gnu.org
Host: powerpc64-unknown-linux-gnu
Target: powerpc64-unknown-linux-gnu
Build: powerpc64-unknown-linux-gnu
FAIL: 25_algorithms/copy/deque_iterators/1.cc execution test
FAIL: 25_algorithms/copy_backward/deque_iterators/1.cc execution test
FAIL: 25_algorithms/move/deque_iterators/1.cc execution test
FAIL: 25_algorithms/move_backward/deque_iterators/1.cc execution test
On gcc110, a 64 processor ppc64 box, the first one completes in 0.23s when
built single-threaded with -O2, but when built with parallel mode and -O2 it
still doesn't complete after 93m40s cpu time. Maybe there's something buggy
about libgomp on ppc64, or maybe the libstdc++ parallel mode just doesn't scale
to lots of processors.