From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E97093858D33; Mon, 28 Aug 2023 13:49:02 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E97093858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1693230542; bh=Cnxt5fMSgHmVDe/XSHnkXYU4m9KIaeqdAIx94o/IOnU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FmApj2o2MkGE0CzNX/PQocDFu5NDkNsksKtvWnB5WUDMeRts3hEELSX16u8Kqz36J sKpQM7F4veajb52AWgycHOXel48jA0qysjeFUVUwGTN3G1EVe1XI4u/eM5VAFf5apn 7L9EryELLJDuaDX8JpwlHJ9jMtWQ4BIWVsv2hxmQ= From: "clyon at gcc dot 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:49:02 +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: clyon 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: 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=3D104167 --- Comment #10 from Christophe Lyon --- (In reply to Jonathan Wakely from comment #9) > (In reply to Christophe Lyon from comment #8) > > On arm-eabi targets (thus, using newlib), we've noticed new errors: >=20 > New since when? These files haven't changed in the last two weeks. The bisection pointed to the patch in comment #6.=