Your message dated Tue, 5 Dec 2017 21:02:25 +0100
with message-id <[email protected]>
and subject line Bug#284988: glibc-doc: CLK_TCK not same as CLOCKS_PER_SEC
has caused the Debian Bug report #284988,
regarding glibc-doc: CLK_TCK not same as CLOCKS_PER_SEC
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
284988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284988
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: glibc-doc
Version: 2.3.2.ds1-18
Severity: normal
In the "CPU Time" node, CLK_TCK is described as an obsolete name for
CLOCKS_PER_SEC. But in Debian (i386 at least) the two are not the
same, eg.
#include <time.h>
main () { printf ("%d %d\n", CLK_TCK, CLOCKS_PER_SEC); }
shows 100 and 1000000.
Perhaps CLK_TCK should move to the "Processor Time" node, since if I'm
not mistaken times() is in units of CLK_TCK per second.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i586)
Kernel: Linux 2.4.25-1-k6
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.16-0experimental1
On 2004-12-10 10:04, Kevin Ryde wrote:
> Package: glibc-doc
> Version: 2.3.2.ds1-18
> Severity: normal
>
> In the "CPU Time" node, CLK_TCK is described as an obsolete name for
> CLOCKS_PER_SEC. But in Debian (i386 at least) the two are not the
> same, eg.
>
> #include <time.h>
> main () { printf ("%d %d\n", CLK_TCK, CLOCKS_PER_SEC); }
>
> shows 100 and 1000000.
>
> Perhaps CLK_TCK should move to the "Processor Time" node, since if I'm
> not mistaken times() is in units of CLK_TCK per second.
This has been fixed in version 2.16, in upstream commit 4cfd80263af2.
Closing the bug.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
[email protected] http://www.aurel32.net
--- End Message ---
