public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/63400] [C++11]precision of std::chrono::high_resolution_clock
Date: Fri, 08 Mar 2024 14:37:08 +0000	[thread overview]
Message-ID: <bug-63400-4-NP9qgGM6H6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63400-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63400

--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Thanks!

So does that mean mingw-w64 fixed the issue by improving the resolution of
CLOCK_REALTIME?
In that case, this bug could be closed WORKSFORME.

Or maybe the testcase makes invalid assumptions and isn't really measuring what
it thinks it's measuring?

In any case, we might want to keep it open to track the suggestion of using
GetSystemTimePreciseAsFileTime for utc_clock, as an enhancement.

  parent reply	other threads:[~2024-03-08 14:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-63400-4@http.gcc.gnu.org/bugzilla/>
2014-09-29  9:33 ` redi at gcc dot gnu.org
2014-09-29 17:18 ` redi at gcc dot gnu.org
2014-09-29 21:00 ` frankhb1989 at gmail dot com
2014-09-29 21:03 ` frankhb1989 at gmail dot com
2014-09-30 10:36 ` redi at gcc dot gnu.org
2022-07-14 18:17 ` redi at gcc dot gnu.org
2022-07-14 18:19 ` redi at gcc dot gnu.org
2022-07-15 10:37 ` redi at gcc dot gnu.org
2024-03-08 10:21 ` redi at gcc dot gnu.org
2024-03-08 10:21 ` redi at gcc dot gnu.org
2024-03-08 11:41 ` redi at gcc dot gnu.org
2024-03-08 13:47 ` vz-gcc at zeitlins dot org
2024-03-08 14:37 ` redi at gcc dot gnu.org [this message]
2024-03-08 14:38 ` redi at gcc dot gnu.org
2024-03-08 15:03 ` vz-gcc at zeitlins dot org

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=bug-63400-4-NP9qgGM6H6@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).