From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: newlib@sourceware.org
Subject: Re: [PATCH] Let RTEMS provide clock()
Date: Wed, 06 Sep 2017 13:06:00 -0000 [thread overview]
Message-ID: <cd075b54-fc1c-1a55-2c79-8f413eb0bfa9@embedded-brains.de> (raw)
In-Reply-To: <20170906084123.GD14453@calimero.vinschen.de>
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.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
next prev parent reply other threads:[~2017-09-06 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 8:53 Sebastian Huber
[not found] ` <20170906084123.GD14453@calimero.vinschen.de>
2017-09-06 13:06 ` Sebastian Huber [this message]
2017-09-06 14:30 ` Joel Sherrill
2017-09-06 15:25 ` Craig Howland
2017-09-07 5:52 ` Sebastian Huber
2017-09-06 13:56 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd075b54-fc1c-1a55-2c79-8f413eb0bfa9@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=newlib@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).