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 468E13858D35; Mon, 28 Aug 2023 13:46:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 468E13858D35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1693230379;
	bh=RNS6esGi64VCocB5DqfianA2C+YkXQmDJa01ceT58Do=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=QPEIk0Qf0mRRVg9R4UMi0vaTt/L54XzLWuZyx2EdCFdfd8/fFLoqCgsj2DcZw2fmL
	 5OzOGWu6VtLs0w4Y2QHGQIy9er1qug8Uh3NxgDumlYPeqy8VBeevnYOdxNnDjvNxKL
	 ki4bIxeefpv5Ylqu5oR5WqTrz/ItENumgPd1DweQ=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104167] Implement C++20 std::chrono::utc_clock,
 std::chrono::tzdb etc.
Date: Mon, 28 Aug 2023 13:46:19 +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: 12.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-104167-4-cGsFEiX7Oz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-104167-4@http.gcc.gnu.org/bugzilla/>
References: <bug-104167-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=3D104167

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Christophe Lyon from comment #8)
> On arm-eabi targets (thus, using newlib), we've noticed new errors:

New since when? These files haven't changed in the last two weeks.=