This is the mail archive of the newlib@sourceware.org mailing list for the newlib 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, RTEMS] Fix CLOCKS_PER_SEC


This patch is correct per POSIX.

http://pubs.opengroup.org/onlinepubs/009695399/functions/clock.html

Gedare addressed the path to our clock() implementation and that should
now be consistent.

I am curious how the #else targets are correct given the POSIX definition.

For RTEMS, is this OK to apply?

--joel

On 3/3/2015 10:24 AM, Gedare Bloom wrote:
> RTEMS use of _SC_CLK_TCK for CLOCKS_PER_SEC is broken [1]. Attached
> patch makes RTEMS use the constant value of 1000000 like Linux and
> BSD.
>
> Gedare
>
> [1] https://devel.rtems.org/ticket/2182

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985


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