public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "atgraham at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/41861]  New: <condition_variable> does not use monotonic_clock
Date: Wed, 28 Oct 2009 23:46:00 -0000	[thread overview]
Message-ID: <bug-41861-12114@http.gcc.gnu.org/bugzilla/> (raw)

<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


             reply	other threads:[~2009-10-28 23:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 23:46 atgraham at gmail dot com [this message]
2009-10-29  0:31 ` [Bug libstdc++/41861] " paolo dot carlini at oracle dot com
2009-11-03 11:22 ` [Bug libstdc++/41861] [C++0x] " paolo dot carlini at oracle dot com
2009-11-03 13:58 ` cfairles at gcc dot gnu dot org
2009-11-03 15:27 ` cfairles at gcc dot gnu dot org
2009-11-03 15:37 ` paolo dot carlini at oracle dot com
2009-11-10  4:38 ` aaron at aarongraham dot com
2010-02-04 18:02 ` paolo dot carlini at oracle dot com
2010-02-05 12:53 ` paolo dot carlini at oracle dot com
2010-02-05 12:53 ` [Bug libstdc++/41861] [DR 887][C++0x] " paolo dot carlini at oracle dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-41861-12114@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).