From: Roland McGrath <roland@redhat.com>
To: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: CLOCK_* clockid_t value macros
Date: Fri, 18 Oct 2002 13:02:00 -0000 [thread overview]
Message-ID: <200210181953.g9IJrQR18599@magilla.sf.frob.com> (raw)
Is there any problem with defining the CLOCK_PROCESS_CPUTIME_ID and
CLOCK_THREAD_CPUTIME_ID macros even on the systems that don't support them?
I would like to consolidate the bits/time.h files and this is the only
actual difference among any of the supported configurations.
It seems fine to me to define them. They are not specified by POSIX.1-2001
(only CLOCK_REALTIME is), but permitted. The spec just says that clock_*
will return EINVAL if given an invalid clockid_t, and so it will for
CLOCK_PROCESS_CPUTIME_ID or CLOCK_THREAD_CPUTIME_ID on systems with no
HP_TIMING support.
I think it's reasonable that programs should need to cope with EINVAL for
these when the macros are present even on machines that currently have
them. One might very well have a libc where e.g. rdtsc has been disabled
for hardware that doesn't support it.
Does anyone see a problem with this?
next reply other threads:[~2002-10-18 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 13:02 Roland McGrath [this message]
2002-10-18 13:09 ` Ulrich Drepper
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=200210181953.g9IJrQR18599@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=libc-hacker@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).