From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Rafael Eduardo Ruviaro Christ
<rafaeleduardoruviaro.christ@asml.com>,
'GNU C Library' <libc-alpha@sourceware.org>
Subject: Re: aarch64 lacks HP_TIMING support in glibc
Date: Mon, 28 Jun 2021 19:25:29 +0000 [thread overview]
Message-ID: <VE1PR08MB5599491B8FD0ED923B7FE28283039@VE1PR08MB5599.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <AM4PR0201MB2227BE4268290DF265342FE88A039@AM4PR0201MB2227.eurprd02.prod.outlook.com>
Hi Rafael,
> Thank you for your message. Currently, we're using glibc 2.28. As soon as I am able to
> update to the latest glibc I will repeat the tests in our platform to evaluate the
> clock_getres() behavior.
I don't believe there has been any change in behaviour since 2.28 - clock_getres does not
use hp-timing in any way (and never did on AArch64). So is there something specific that
you have an issue with?
Cheers,
Wilco
next prev parent reply other threads:[~2021-06-28 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 11:43 Wilco Dijkstra
2021-06-23 13:26 ` Adhemerval Zanella
2021-06-23 15:19 ` Wilco Dijkstra
2021-06-28 15:49 ` Rafael Eduardo Ruviaro Christ
2021-06-28 19:25 ` Wilco Dijkstra [this message]
2021-06-30 13:27 ` Rafael Eduardo Ruviaro Christ
2021-07-02 13:13 ` Wilco Dijkstra
2021-07-02 13:53 ` Adhemerval Zanella
-- strict thread matches above, loose matches on Subject: below --
2021-06-22 18:29 Rafael Eduardo Ruviaro Christ
2021-06-22 18:38 ` Andrew Pinski
2021-06-22 18:57 ` Adhemerval Zanella
2021-06-22 19:27 ` Andreas Schwab
2021-06-22 19:53 ` Adhemerval Zanella
2021-06-22 20:18 ` Andreas Schwab
2021-06-22 20:22 ` Adhemerval Zanella
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=VE1PR08MB5599491B8FD0ED923B7FE28283039@VE1PR08MB5599.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=rafaeleduardoruviaro.christ@asml.com \
/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).