From: Andrew Pinski <pinskia@gmail.com>
To: Rafael Eduardo Ruviaro Christ <rafaeleduardoruviaro.christ@asml.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: aarch64 lacks HP_TIMING support in glibc
Date: Tue, 22 Jun 2021 11:38:48 -0700 [thread overview]
Message-ID: <CA+=Sn1nNfa2nrYzS0PdtCTX0K=2d5YD7cyVm7G7GQCZ=ZEbfoQ@mail.gmail.com> (raw)
In-Reply-To: <AM4PR0201MB2227C93ACDF20EF7D9A46F528A099@AM4PR0201MB2227.eurprd02.prod.outlook.com>
On Tue, Jun 22, 2021 at 11:30 AM Rafael Eduardo Ruviaro Christ via
Libc-alpha <libc-alpha@sourceware.org> wrote:
>
> Hello,
>
> I noticed that aarch64 lacks HP_TIMING support in glibc. Although this architecture has generic timers, glibc is still using the generic hp-timing.h for aarch64.
> I see HP_TIMING support for other architectures. I'd like to know why there is no HP_TIMING support for aarch64?
> Also, if there's planning to support it for aarch64?
See https://sourceware.org/legacy-ml/libc-alpha/2015-06/msg00736.html
and the previous emails in the thread.
Thanks,
Andrew Pinski
>
>
> Thank you,
> Kind regards,
> Rafael
> -- The information ....
This disclaimer is useless for public lists, remove it.
next prev parent reply other threads:[~2021-06-22 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 18:29 Rafael Eduardo Ruviaro Christ
2021-06-22 18:38 ` Andrew Pinski [this message]
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
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
2021-06-30 13:27 ` Rafael Eduardo Ruviaro Christ
2021-07-02 13:13 ` Wilco Dijkstra
2021-07-02 13:53 ` 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='CA+=Sn1nNfa2nrYzS0PdtCTX0K=2d5YD7cyVm7G7GQCZ=ZEbfoQ@mail.gmail.com' \
--to=pinskia@gmail.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).