From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-305082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 32567 invoked by alias); 12 Jan 2010 16:35:13 -0000
Received: (qmail 32437 invoked by uid 48); 12 Jan 2010 16:35:00 -0000
Date: Tue, 12 Jan 2010 16:35:00 -0000
Subject: [Bug libstdc++/42712]  New: search_n/iterator.cc times out in parallel-mode
X-Bugzilla-Reason: CC
Message-ID: <bug-42712-16141@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2010-01/txt/msg01389.txt.bz2

I'm consistently seeing this time out when regtesting make check-parallel. Is
it unavoidable withing the current infrastructure? Besides slowing down the
testing itself (not a very big issue, momentarily, I will commit an hack for
this), seems a quite puzzling behavior to me: if parallel-mode runs orders of
magnitude slower than serial-mode, shouldn't in principle at minimum fall back
to the latter?


-- 
           Summary: search_n/iterator.cc times out in parallel-mode
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: paolo dot carlini at oracle dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42712