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 D68803858C5E; Thu,  2 Mar 2023 23:50:32 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D68803858C5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677801032;
	bh=jm8Luk9qeam1bnQWB9FXCyhEnCeFrQMxB+vA2k+yaEo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=TLaXK8RQCKM8t1Jj0pgKDdwFX91xJh+jjOGvr5c9LWycVDXWREVtm3DB2htQoyL3M
	 oQrUdzYpmMICrxQTjyDv1d+ZefJtZimPrm+UBtOcAb5yjQ1Bx2BVmuXGtAJHsnur9N
	 0tyfuERcGypVuYMUVqrvGZXzdDn8I7DwviOJjNyM=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/108865] gcc on Windows fails with Unicode path to source
 file
Date: Thu, 02 Mar 2023 23:50:32 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108865-4-13qsVayvuz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108865-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=3D108865

--- Comment #16 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Costas Argyris from comment #15)
> Sounds like I am hitting a separate existing limitation that has nothing =
to
> do with this bug.
>=20
> Do we need a new bug report for that one then?

No one bug report is enough really in this case.=20
It should not be hard to come up with a secondary patch which fixes that is=
sue.
I might give it a go in a few weeks if someone has not already.=