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 C21723858D38; Mon, 23 Jan 2023 11:50:06 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C21723858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1674474606;
	bh=5K5fFW2KTcUBZEbPyxljQTBhVepnhEgaiyfngObVweQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=sKv1y3eZJF0TxPvbwULh7nhfsCONI36qLtizK/xckxal0O50ZBhLh1JEBFx0sMv2i
	 YralxL4mJaUL7zsrBK9MzlW/HFnd/EDVW+2n+bq6GwpYtPdo1+duMwbvqkK7hmZKqA
	 qGVlp2wK3m8Nrx4KqRBr/nqZgMtR2/wJKZSQxXlA=
From: "i.nixman at autistici dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/108350] Windows: invoking gcc via symlink does not work
Date: Mon, 23 Jan 2023 11:50:06 +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: 12.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: i.nixman at autistici dot org
X-Bugzilla-Status: UNCONFIRMED
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-108350-4-I7aV6HLzpq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108350-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108350-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=3D108350

--- Comment #34 from niXman <i.nixman at autistici dot org> ---
(In reply to Bill Zissimopoulos from comment #33)
> Now that we have a potential patch what are the steps to get it included
> into the gcc codebase?

great question!
I think the best option is to give me rights to merge =3D)=