From: Ulrich Drepper <drepper@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: CLOCK_* clockid_t value macros
Date: Fri, 18 Oct 2002 13:09:00 -0000 [thread overview]
Message-ID: <3DB06970.8080604@redhat.com> (raw)
In-Reply-To: <200210181953.g9IJrQR18599@magilla.sf.frob.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Roland McGrath wrote:
> 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.
In theory it shouldn't be a problem since users have to check
_POSIX_CPUTIME and _POSIX_THREAD_CPUTIME first. But there is definitely
code out there which will break. I don't have personally problems with
this.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9sGlw2ijCOnn/RHQRAgk2AJ0V0+mzZx5GRgaOVhxA00amaR5uAgCfUz7t
miCO9JQ1hWNrOJuI5vOxEmw=
=pvYV
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2002-10-18 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 13:02 Roland McGrath
2002-10-18 13:09 ` Ulrich Drepper [this message]
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=3DB06970.8080604@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).