This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/57641] std::timed_mutex.try_lock_until() is broken
- 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, 18 Jun 2013 16:58:37 +0000
- Subject: [Bug libstdc++/57641] std::timed_mutex.try_lock_until() is broken
- Auto-submitted: auto-generated
- References: <bug-57641-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57641
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I agree that code assumes the epochs are the same, but what you describe
doesn't make sense since high_resolution_clock and steady_clock have the same
epoch in our implementation. Are you seeing the first problem described at PR
54562?
Do you have a testcase?