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 B57733858C2A; Wed, 15 Nov 2023 13:16:16 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B57733858C2A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1700054176;
	bh=DQ+MM7/vo9/FOw6sCsT9pSjxAY+ZTiAg+N3aCfiy7rE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=h8n8iF24QJlx/DlXTbf1Q8FJfQc3mKn7kelDecr1qszJ4RUOwQV+5OCqWVjWJGdV6
	 Gio0RYZcwzHcL7lwygG1dOUGQXVC3XXmc1d67FB6It5HnN8DKBIDbHIEVlBhu9CniC
	 eyw3iacIFIU86BPYFg730GmltMJmxD+p1ZcoPTVc=
From: "costas.argyris at gmail dot com" <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: Wed, 15 Nov 2023 13:16:15 +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: costas.argyris at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108865-4-os9RwaQmLz@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 #40 from Costas Argyris <costas.argyris at gmail dot com> ---
(In reply to Eric Botcazou from comment #39)
> FWIW this also breaks the GNAT_CODE_PAGE feature of the Ada compiler (whi=
ch
> is arguably a kludge) so providing a configure option to revert to the old
> setting would indeed be in order here.

I can try coming up with a patch to introduce a new windows-host-specific
configure option to exclude the utf8 manifest on demand, but that won't be =
for
a while...

I'm curious though: How come it took so long to report this one?    Is this=
 a
rarely-used feature of the Ada compiler?    It seems strange that a feature=
 of
the compiler would interact so strongly with the active code page being use=
d by
the compiler process at runtime.=