public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15555] pthread_condattr_setclock should accept CLOCK_MONOTONIC_COARSE Date: Sat, 01 Jun 2013 01:15:00 -0000 [thread overview] Message-ID: <bug-15555-131-3SRA0BzhI8@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15555-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15555 Rich Felker <bugdal at aerifal dot cx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugdal at aerifal dot cx --- Comment #1 from Rich Felker <bugdal at aerifal dot cx> --- Due to the way it's implemented, the only clocks that can be supported are the realtime and monotonic clocks. However, as POSIX only documents an error for cpu-time-based clocks, not other implementation-defined clocks, I think it would be nice to support as many as possible. The course versions of realtime and monotonic could simply be remapped to the respective non-course versions and would work fine. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-06-01 1:15 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-31 17:46 [Bug libc/15555] New: " bernd.schubert at fastmail dot fm 2013-06-01 1:15 ` bugdal at aerifal dot cx [this message] 2014-02-07 3:17 ` [Bug nptl/15555] " jsm28 at gcc dot gnu.org 2014-06-13 17:34 ` fweimer at redhat dot com 2021-10-21 15:42 ` [Bug nptl/15555] pthread_condattr_setclock should accept CLOCK_MONOTONIC_COARSE, CLOCK_MONOTONIC_RAW fweimer at redhat dot com
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=bug-15555-131-3SRA0BzhI8@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe 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).