From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id BC64E3858D38; Fri,  8 Mar 2024 14:37:08 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BC64E3858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1709908628;
	bh=H/n/veA9ah1JCBIZUXw5JutT6u5uZ5yZoHWQk5pTRww=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=kMNiLNKy4hbbxUurGqGwonxXaCpNNeqGeWyiolAxQyQ6LwiCKEh9Bxvz0BAIrmoxC
	 QM2dlPYNitZ4zUiMKJRGRtpJVL5xUm4RZwUDLKzXCoCzvRUrVhuCFyo4g7LdA+7DCp
	 ItU4koCJSibPvRsc6Vb0VMmfDq2TeBje24rLav04=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.9.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: minor
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-63400-4-NP9qgGM6H6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63400-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63400-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- 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.=