From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-297856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 27171 invoked by alias); 28 Oct 2009 23:46:55 -0000
Received: (qmail 27068 invoked by uid 48); 28 Oct 2009 23:46:32 -0000
Date: Wed, 28 Oct 2009 23:46:00 -0000
Subject: [Bug libstdc++/41861]  New: <condition_variable> does not use monotonic_clock
X-Bugzilla-Reason: CC
Message-ID: <bug-41861-12114@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "atgraham at gmail 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: 2009-10/txt/msg02418.txt.bz2

<mutex> looks like this:

171     #ifdef _GLIBCXX_USE_CLOCK_MONOTONIC
172         typedef chrono::monotonic_clock             __clock_t;
173     #else
174         typedef chrono::high_resolution_clock       __clock_t;
175     #endif

...but <condition_variable> only has this:

56          typedef chrono::system_clock        __clock_t;

Shouldn't <condition_variable> be using the monotonic_clock if available, just
like <mutex>?


-- 
           Summary: <condition_variable> does not use monotonic_clock
           Product: gcc
           Version: 4.4.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: atgraham at gmail dot com


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