public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernd.schubert at fastmail dot fm" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15555] New: pthread_condattr_setclock should accept CLOCK_MONOTONIC_COARSE
Date: Fri, 31 May 2013 17:46:00 -0000	[thread overview]
Message-ID: <bug-15555-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=15555

            Bug ID: 15555
           Summary: pthread_condattr_setclock should accept
                    CLOCK_MONOTONIC_COARSE
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: bernd.schubert at fastmail dot fm
                CC: drepper.fsp at gmail dot com

I just tried to use pthread_condattr_setclock() and CLOCK_MONOTONIC_COARSE but 
that unexpectedly failed. So I checked the glibc code and noticed that only
CLOCK_MONOTONIC and CLOCK_REALTIME are supported. I'm not sure about the
clock_ids, but at least CLOCK_REALTIME_COARSE and CLOCK_MONOTONIC_COARSE should
be supported. 
Probably only CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID should be
forbidden, similar as musl libc does it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2013-05-31 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 17:46 bernd.schubert at fastmail dot fm [this message]
2013-06-01  1:15 ` [Bug libc/15555] " bugdal at aerifal dot cx
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@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: 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).