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 435E93858D32; Fri, 10 Nov 2023 20:47:09 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 435E93858D32
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1699649229;
	bh=CVOzDswWGTjFYFfxqCu7blPzTxYnSNqSRI96Od6lGhA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=cc8EVuIxloQam9SjceRTjzpE9D5/dMRMHNipbzK9IQW+VTl/IdTptNQ9fVkLbQ68/
	 0DoL+kxKYZjqZvwkXwW2AEpD+u8GFjacAR44EkMiK0Nt6GU11CWjiy9Vlj1LRiBe+2
	 Pe2ATZP9x2ujsFqmp9/fR5tGOeMMZL/PY1TODjII=
From: "gaius at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/110779] SysClock can not read the clock
Date: Fri, 10 Nov 2023 20:47:09 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: modula2
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gaius at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: gaius at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110779-4-flUADiEMuS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110779-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110779-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=3D110779

--- Comment #21 from Gaius Mulley <gaius at gcc dot gnu.org> ---
I've just noticed that the patch doesn't address the issue of
GLIBCXX_IS_NATIVE.=