public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/53841] [C++11] condition_variable::wait_until() fails with high resolution clocks Date: Wed, 14 Nov 2012 23:14:00 -0000 [thread overview] Message-ID: <bug-53841-4-UYaJEyilzw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53841-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53841 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2012-11-14 Ever Confirmed|0 |1 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-11-14 23:14:22 UTC --- (In reply to comment #3) > - const chrono::nanoseconds __delta = __atime - __c_entry; > - const __clock_t::time_point __s_atime = __s_entry + __delta; > + const auto __delta = __atime - __c_entry; > + const auto __s_atime = __s_entry + __delta; Thanks for this. > Clang trunk currently rejects this code (prior to instantiation, even) due to > this invalid conversion if _GLIBCXX_USE_CLOCK_REALTIME is not defined (as seems > to be the case on several popular linux distributions). That's not defined on GNU/Linux unless you build GCC with --enable-libstdcxx-time=rt, which has performance implications.
next prev parent reply other threads:[~2012-11-14 23:14 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-03 15:59 [Bug libstdc++/53841] New: " redi at gcc dot gnu.org 2012-07-03 16:06 ` [Bug libstdc++/53841] " redi at gcc dot gnu.org 2012-07-03 16:15 ` redi at gcc dot gnu.org 2012-11-14 23:06 ` richard-gccbugzilla at metafoo dot co.uk 2012-11-14 23:14 ` redi at gcc dot gnu.org [this message] 2012-11-15 0:56 ` redi at gcc dot gnu.org 2012-11-15 1:38 ` redi at gcc dot gnu.org 2012-11-15 1:56 ` redi at gcc dot gnu.org 2012-11-15 1:58 ` redi at gcc dot gnu.org
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-53841-4-UYaJEyilzw@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: linkBe 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).