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] Let RTEMS provide clock()

From: Joel Sherrill <joel dot sherrill at oarcorp dot com>
To: Sebastian Huber <sebastian dot huber at embedded-brains dot de>, "newlib at sourceware dot org" <newlib at sourceware dot org>
Date: Wed, 6 Sep 2017 08:56:02 -0500
Subject: Re: [PATCH] Let RTEMS provide clock()
Authentication-results: sourceware.org; auth=none
References: <20170906065845.13573-1-sebastian.huber@embedded-brains.de> <20170906084123.GD14453@calimero.vinschen.de> <cd075b54-fc1c-1a55-2c79-8f413eb0bfa9@embedded-brains.de>



On 9/6/2017 3:53 AM, Sebastian Huber wrote:

On 06/09/17 10:41, Corinna Vinschen wrote:

I just don't quite understand.  Is sysconf(_SC_CLK_TCK) different
from CLOCKS_PER_SEC on RTEMS?


Yes, the CLOCKS_PER_SEC is a POSIX defined constant and the
sysconf(_SC_CLK_TCK) returns the actual system tick frequency. Which is
usually 100 or 1000 ticks per second.


Making it more complicated, the system tick frequency is
something that the end user can set for each application.
We just need to make sure that the constant CLOCKS_PER_SECOND
is appropriate for use with clock() as defined here:

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

Sebastian.. I assume that all that matches up per POSIX, right?

--joel

Follow-Ups:
- Re: [PATCH] Let RTEMS provide clock()
  - From: Craig Howland

References:
- [PATCH] Let RTEMS provide clock()
  - From: Sebastian Huber
- Re: [PATCH] Let RTEMS provide clock()
  - From: Sebastian Huber

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