public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "johnstul at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11389] New: bits/time.h missing CLOCK_MONOTONIC_RAW, CLOCK_REALTIME_COARSE, and CLOCK_MONOTONIC_COARSE
Date: Tue, 16 Mar 2010 22:39:00 -0000 [thread overview]
Message-ID: <20100316223905.11389.johnstul@us.ibm.com> (raw)
Linux has introduced some additional clockids, and glibc has not yet included
them from linux/include/time.h
The new clockids are:
#define CLOCK_MONOTONIC_RAW 4 /* since 2.6.28 */
#define CLOCK_REALTIME_COARSE 5 /* since 2.6.32 */
#define CLOCK_MONOTONIC_COARSE 6 /* since 2.6.32 */
--
Summary: bits/time.h missing CLOCK_MONOTONIC_RAW,
CLOCK_REALTIME_COARSE, and CLOCK_MONOTONIC_COARSE
Product: glibc
Version: 2.10
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: johnstul at us dot ibm dot com
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=11389
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-03-16 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 22:39 johnstul at us dot ibm dot com [this message]
2010-04-04 2:29 ` [Bug libc/11389] " drepper 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=20100316223905.11389.johnstul@us.ibm.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.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).