From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0EECE3857427; Tue, 25 Oct 2022 11:54:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0EECE3857427 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666698878; bh=APhFJum1DaB9vI6jc8rd9Ps3U0zF/eiU3YNPbMU0pT8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=e8W25Pv53aIwF6PfpvZBmWe/PFkqCleIWsAu1qsreVuoUIUAOBUg9z+OQxMsDuqWl MZZ8RQcT8pZaO9PR1kagSnbeMtFn2An96YT7+UzenngpY88yCb1ehES/e1Eb38sxiq xJC72rz/+t9NHWFXq++azX+uyqoeK7ii7jpr9LY4= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/95048] [10/11/12/13 Regression] wstring-constructor of std::filesystem::path throws for non-ASCII characters Date: Tue, 25 Oct 2022 11:54: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: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.5 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=3D95048 --- Comment #16 from Jonathan Wakely --- Thanks. As per https://gcc.gnu.org/lists.html patches for libstdc++ need to= be CC'd to the libstdc++ list, but I'll find it in the gcc-patches archive and review it ASAP. I'm still concerned that this just moves the problem, so that different cas= es fail instead. But maybe it's an improvement for the most common case, and i= t's better to fail in the rare situations.=