This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 12/12] Revise the documentation of ʽsimple calendar timeʼ.
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Paul Eggert <eggert at cs dot ucla dot edu>
- Cc: Zack Weinberg <zackw at panix dot com>, <libc-alpha at sourceware dot org>, Florian Weimer <fweimer at redhat dot com>, Lukasz Majewski <lukma at denx dot de>, Alistair Francis <alistair23 at gmail dot com>, Stepan Golosunov <stepan at golosunov dot pp dot ru>, Arnd Bergmann <arnd at arndb dot de>
- Date: Tue, 20 Aug 2019 19:38:21 +0000
- Subject: Re: [PATCH 12/12] Revise the documentation of ʽsimple calendar timeʼ.
- Ironport-sdr: /qbfM7r00u/AmKlZuN37mpwRiTDDjogH0OMEX4Xbm3Xl4GMLJkwFJwYcgkpjAEZzbIZgfb3T68 Mey3q1QNsnXqhteS6mWWHNJOcAjgsnPRhZ9rUuZ9UJB6bP1F1RmgErfPwMEZDx5bjuAkfClPbJ 6iQODMpd8ue143BIqR169DXn6UQWU5hI7B+Uz4sMMBkUitoduOKPxHbZlAI3/C6iLxzE15bCGz ZMBfyaXJSSf9CvXG6qZkSnTFCYrUg7t3NO3j7quNegwKWGZzttWyCgsG1EgV8nYC/0pBix9nYf n8U=
- Ironport-sdr: qYgftBQGBDgdjT7YvgC0AkSG4Bu8DP87UVwR2Rr3yc7qS14CwDauOaLTlOygThIqTWtaoEu9ol pqckJ8oWXrolVZc5EKwD/ILc5BArMdxRyl2wAFnd1dUSsgz4Ha1IKyYxCbJ2Gkk7NBROQ2DZ8Z o0anYnC7tHUmSJoMnm8vXgp2eXRBmeIuAdhwdESuLZS1J3egOXB48keSjfmDq1J3WLAgWK+Y1T 3qNKK0j45k2gYsgON5I0nao967NKQJ433t8lzlWcJZjMrs7SBQdKloQ0kLPUXT9XqLXO8JHp/J +ys=
- References: <20190820132152.24100-1-zackw@panix.com> <20190820132152.24100-13-zackw@panix.com> <e629c22a-9b1e-bda8-5c9f-a1951cfee96f@cs.ucla.edu>
On Tue, 20 Aug 2019, Paul Eggert wrote:
> Zack Weinberg wrote:
> > +@code{clock_t} is used to measure processor and CPU time. Its values
> > +are counts of @dfn{clock ticks} since some arbitrary event. The
> > +number of clock ticks per second is system-specific.
>
> Also mention here that ISO C and POSIX both say that clock_t may be an an
> integer or a floating-point type.
I think the key fact about clock_t is that it (and so the functions using
it) should be avoided because of limited range on many systems and
getrusage should be used instead. That's mentioned in the manual, but
perhaps not given enough emphasis.
--
Joseph S. Myers
joseph@codesourcery.com