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 0ED66385741A; Tue, 25 Oct 2022 12:47:11 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0ED66385741A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1666702031;
	bh=7Elg3pjrTVlzfBRe4f+djCp64u2XTOeFOXl01oA3EU8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=OSymkbk8Hk6C10tHMznM0YLd0NRhhLwLfewDJjROod8A4cGQg6qEG2ZLPkZWvOxcP
	 4SJwXQXBnKdPWuBlFIlb+Yo8qMD7wb6LtqhPfFreUAMvyB7zzkq0aTDO/C0M+HcKtV
	 cj9RHkbDRW/uQ9y9gztwUFNJwL8y2igQTliKQkdo=
From: "ulf.lorenz at ptvgroup dot com" <gcc-bugzilla@gcc.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 12:47:10 +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: ulf.lorenz at ptvgroup dot com
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: <bug-95048-4-TaSnnzL2Z0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95048-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95048-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=3D95048

--- Comment #17 from Ulf Lorenz <ulf.lorenz at ptvgroup dot com> ---
Your point was an item during implementation. Besides the other cases being
rare and probably exotic, the killer argument was that it would be way more
complex. While I am confident now that I can move around the libstdc++ sour=
ce
code reasonably well and do simple patches and working tests, understanding
iconv and the required acceptance_tests_with_special_compilation_flags requ=
ires
considerable more time budget than I have needed so far.

I agree that this is not the bullet-proof solution, though, but only an
incremental improvement.=