r278900 - in /trunk/libstdc++-v3: ChangeLog tes...

[redi@gcc.gnu.org]

Author: redi
Date: Mon Dec  2 16:22:53 2019
New Revision: 278900

URL: https://gcc.gnu.org/viewcvs?rev=278900&root=gcc&view=rev
Log:
libstdc++: Improve tests for try_lock_until members of mutex types

2019-12-02  Mike Crowe  <mac@mcrowe.com>

	* testsuite/30_threads/recursive_timed_mutex/try_lock_until/3.cc:
	New test. Ensure that timed_mutex::try_lock_until actually times out
	after the specified time when using both system_clock and
	steady_clock.
	* testsuite/30_threads/timed_mutex/try_lock_until/3.cc: New test.
	Likewise but for recursive_timed_mutex.
	* testsuite/30_threads/timed_mutex/try_lock_until/57641.cc: Template
	test functions and use them to test both steady_clock and system_clock.
	* testsuite/30_threads/unique_lock/locking/4.cc: Likewise. Wrap call
	to timed_mutex::try_lock_until in VERIFY macro to check its return
	value.

Added:
    trunk/libstdc++-v3/testsuite/30_threads/recursive_timed_mutex/try_lock_until/3.cc
      - copied, changed from r278894, trunk/libstdc++-v3/testsuite/30_threads/unique_lock/locking/4.cc
    trunk/libstdc++-v3/testsuite/30_threads/timed_mutex/try_lock_until/3.cc
      - copied, changed from r278894, trunk/libstdc++-v3/testsuite/30_threads/unique_lock/locking/4.cc
Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/testsuite/30_threads/timed_mutex/try_lock_until/57641.cc
    trunk/libstdc++-v3/testsuite/30_threads/unique_lock/locking/4.cc