From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9812C385C6F7; Fri, 8 Mar 2024 10:21:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9812C385C6F7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709893294; bh=Trge1JoNzOBqT2m0i/1NWr+asGsiRbIBfUc0xzubKDQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=tb97EWrYjw6bIFGOHTF6LlYjHAKTfwTLjqOpeHTBkj0BhHYnj+PhNZO19WIhA7vSV 5kuld5+BtHDiMxuVdXyVferozG4LNPO/FywfDE/Pa+5/SFYCZy9dIn3sPcRo+FZ+TP +M5nIJpdAD7rrhvNCf/HB7XiLK5WGEbavTNSinJY= From: "redi at gcc dot 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 10:21:33 +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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D63400 --- Comment #11 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #8) > Is this still an issue in 2022? >=20 > Using a mingw-w64 cross-compiler and running under Wine I get: >=20 > CLOCK_REALTIME: 0,100 > CLOCK_MONOTONIC: 0,100 >=20 > Is that just because I'm using Wine not real Windows? I still want an answer to this question though.=