This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH v2][BZ #12515] Improve precision of clock function


On 05/21/13 13:45, Steven Munroe wrote:
>> If that isn't clear, perhaps we can prepend a line like the
>> > following, to make it clear:
>> > 
>> >    static_assert (1000000000 % CLOCKS_PER_SEC == 0);
>> > 
> That assume that __clock_gettime (CLOCK_REALTIME,) and CLOCKS_PER_SEC
> are multiples of 10. 
> 
> "Although the value of CLOCKS_PER_SEC is required to be 1 million on all
> XSI-conformant systems, it may be variable on other systems, and it
> should not be assumed that CLOCKS_PER_SEC is a compile-time constant."

We're talking about code in the GNU C library, right?
There, CLOCKS_PER_SEC is guaranteed to be a compile-time constant
that is equal to 1 million.  The static_assert is meant
merely as a memory aid, to make things clear; it's guaranteed
to succeed.

There's no assumption here that clock_gettime returns a multiple
of 10, or of CLOCKS_PER_SEC.  For example, if clock_gettime
returns tv_sec == 975 and tv_nsec = 123456789, then the
expression (ts.tv_sec * CLOCKS_PER_SEC + ts.tv_nsec /
(1000000000 / CLOCKS_PER_SEC)) returns 975 * 1000000
+ 123456789 / 1000, which is 975123456, which is the
correct value.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]