unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Mike Crowe <mac@mcrowe.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH 0/7] Implement proposed POSIX _clockwait variants of existing _timedwait functions
Date: Mon, 11 Mar 2019 23:13:46 +0000	[thread overview]
Message-ID: <alpine.DEB.2.21.1903112312160.28233@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20190310091255.dfr7r4nys6cve5uf@mcrowe.com>

On Sun, 10 Mar 2019, Mike Crowe wrote:

> It would be straightforward to add them with support for CLOCK_REALTIME
> only, but I'm not sure that it really brings much value. Adding
> CLOCK_MONOTONIC support at the same time as the new functions would mean
> that autoconf scripts would know that CLOCK_MONOTONIC was supported if the
> functions were found, rather than having to fall back at runtime.

No, they wouldn't know that, if kernel support is needed for 
CLOCK_MONOTONIC support, because the kernel at runtime might be too old 
(glibc generally supports at least the oldest active LTS kernel series).

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2019-03-11 23:13 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 18:23 [PATCH 0/7] Implement proposed POSIX _clockwait variants of existing _timedwait functions Mike Crowe
2019-02-27 18:23 ` [PATCH 1/7] nptl: Add clockid parameter to futex timed wait calls Mike Crowe
2019-03-05 12:39   ` Adhemerval Zanella
2019-03-10  8:59     ` Mike Crowe
2019-03-11 11:50       ` Adhemerval Zanella
2019-02-27 18:23 ` [PATCH 2/7] nptl: Add POSIX-proposed sem_clockwait Mike Crowe
2019-02-27 18:35   ` Joseph Myers
2019-03-05 13:31   ` Adhemerval Zanella
2019-03-10 16:17     ` Mike Crowe
2019-03-19 17:07       ` Adhemerval Zanella
2019-03-14 14:09   ` Yann Droneaud
2019-03-14 14:39     ` Mike Crowe
2019-02-27 18:23 ` [PATCH 3/7] nptl: Add POSIX-proposed pthread_cond_clockwait Mike Crowe
2019-03-05 16:45   ` Adhemerval Zanella
2019-05-04 20:22     ` Mike Crowe
2019-02-27 18:23 ` [PATCH 4/7] nptl: pthread_rwlock: Move timeout validation into _full functions Mike Crowe
2019-03-05 16:48   ` Adhemerval Zanella
2019-02-27 18:23 ` [PATCH 5/7] nptl/tst-rwlock14: Test pthread/rwlock_timedwrlock correctly Mike Crowe
2019-03-05 17:36   ` Adhemerval Zanella
2019-02-27 18:23 ` [PATCH 6/7] nptl/tst-rwlock: Use clock_gettime/timespec rather than gettimeofday/timeval Mike Crowe
2019-03-05 18:02   ` Adhemerval Zanella
2019-03-20 21:34     ` Mike Crowe
2019-03-14 14:44   ` Yann Droneaud
2019-02-27 18:23 ` [PATCH 7/7] nptl: Add POSIX-proposed pthread_rwlock_clockrdlock & pthread_rwlock_clockwrlock Mike Crowe
2019-03-07 12:59   ` Adhemerval Zanella
2019-03-05 12:35 ` [PATCH 0/7] Implement proposed POSIX _clockwait variants of existing _timedwait functions Adhemerval Zanella
2019-03-06 21:15   ` Joseph Myers
2019-03-10  9:12     ` Mike Crowe
2019-03-11 23:13       ` Joseph Myers [this message]
2019-03-13 21:42   ` Mike Crowe
2019-03-14 11:30     ` Adhemerval Zanella
2019-03-15 13:25 ` Yann Droneaud
2019-03-15 13:36   ` Mike Crowe

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1903112312160.28233@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mac@mcrowe.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).