From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27068 invoked by alias); 11 Nov 2013 13:33:57 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 26889 invoked by uid 55); 11 Nov 2013 13:33:53 -0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/54562] mutex and condition variable timers Date: Mon, 11 Nov 2013 13:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 4.7.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-11/txt/msg01054.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54562 --- Comment #5 from Jonathan Wakely --- Author: redi Date: Mon Nov 11 13:33:48 2013 New Revision: 204672 URL: http://gcc.gnu.org/viewcvs?rev=204672&root=gcc&view=rev Log: PR libstdc++/54562 * include/std/mutex (__timed_mutex_impl::__clock_t): Use high_resolution_clock for absolute timeouts, because pthread_mutex_timedlock uses CLOCK_REALTIME not CLOCK_MONOTONIC. (__timed_mutex_impl::_M_try_lock_for): Use steady_clock for relative timeouts as per [thread.req.timing]. (__timed_mutex_impl::_M_try_lock_until): Convert to __clock_t time point instead of using _M_try_lock_for. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/std/mutex