public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Torvald Riegel <triegel@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [patch] Fix shared_timed_mutex::try_lock_until() et al
Date: Fri, 10 Apr 2015 10:21:00 -0000	[thread overview]
Message-ID: <20150410102132.GY9755@redhat.com> (raw)
In-Reply-To: <1428659777.2909.1.camel@triegel.csb>

On 10/04/15 11:56 +0200, Torvald Riegel wrote:
>Ah, right.  I was confused by the name, thinking those targets don't
>support pthread_mutex_timedlock, not pthread_rwlock_timedrdlock etc.

The macro actually relates to the _POSIX_TIMEOUTS macro, but was
originally added to check for pthread_mutex_timedlock support, hence
its name. Maybe a better name would be _GLIBCXX_USE_MUTEX_TIMEOUTS.

Both pthread_mutex_timedlock and pthread_rwlock_timed??lock were
originally part of the POSIX Timeouts option, so on older POSIX
systems they are only available when _POSIX_TIMEOUTS is defined.
(They are part of the base spec in the current POSIX standard, but
Darwin and HPUX don't implement that and still treat them as
optional.)

  reply	other threads:[~2015-04-10 10:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 14:28 Jonathan Wakely
2015-04-08 16:59 ` Torvald Riegel
2015-04-08 19:12   ` Jonathan Wakely
2015-04-08 19:38     ` Jonathan Wakely
2015-04-10  0:16       ` Torvald Riegel
2015-04-10  8:38         ` Jonathan Wakely
2015-04-10  9:56           ` Torvald Riegel
2015-04-10 10:21             ` Jonathan Wakely [this message]
2015-04-10  0:11     ` Torvald Riegel
2015-04-11 11:48     ` Jonathan Wakely

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=20150410102132.GY9755@redhat.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=triegel@redhat.com \
    /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: link
Be 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).