diff options
| author | Mike Crowe <mac@mcrowe.com> | 2018-08-01 15:39:57 +0000 |
|---|---|---|
| committer | Jonathan Wakely <redi@gcc.gnu.org> | 2018-08-01 16:39:57 +0100 |
| commit | 9e68aa3cc52956ea99bb726c3c29ce0581b9f7e7 (patch) | |
| tree | 823a9f37c46670bcc8fb5298f87b86f0029d25d0 /gcc/cfgexpand.c | |
| parent | 2f5934326542b3f303db91cc4cd432cd488f0258 (diff) | |
| download | gcc-9e68aa3cc52956ea99bb726c3c29ce0581b9f7e7.zip gcc-9e68aa3cc52956ea99bb726c3c29ce0581b9f7e7.tar.gz gcc-9e68aa3cc52956ea99bb726c3c29ce0581b9f7e7.tar.bz2 | |
Use steady_clock to implement condition_variable::wait_for
The C++ standard says that std::condition_variable::wait_for should be
implemented to be equivalent to:
return wait_until(lock, chrono::steady_clock::now() + rel_time);
But the existing implementation uses chrono::system_clock. Now that
wait_until has potentially-different behaviour for chrono::steady_clock,
let's at least try to wait using the correct clock.
2018-08-01 Mike Crowe <mac@mcrowe.com>
* include/std/condition_variable (wait_for): Use steady_clock.
From-SVN: r263225
Diffstat (limited to 'gcc/cfgexpand.c')
0 files changed, 0 insertions, 0 deletions