This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/15555] New: pthread_condattr_setclock should accept CLOCK_MONOTONIC_COARSE


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]