From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3929C3858C62; Sat, 24 Jun 2023 20:14:11 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3929C3858C62 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1687637651; bh=uu9bhcFWaw4MJWolcdEYwAoOLmF44f8ZbDOtJz8vz+k=; h=From:To:Subject:Date:In-Reply-To:References:From; b=S08OrCLxgqBEMIAEoP2sPF30VsbYalXMUy6aFhUDwYTDn1Ut7q0ztuCT++Ja0gvRs FcRpzyKCNpieDTcBn1YmG+11B2I0aU5OGBdqAX5ze8zOiapIpuIftUks/4OPNgcmWO DzPB6/CpTmUEKxd3MfrcOMJCoHAf9GoYOvhUkYqY= From: "brechtsanders at users dot sourceforge.net" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32 Date: Sat, 24 Jun 2023 20:14:11 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: brechtsanders at users dot sourceforge.net 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: 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=3D108678 --- Comment #3 from Brecht Sanders --- Any pointers on which files to edit in order to support aarch64-mingw ? I think it won't require reinventing the wheel as it will probably be a mix= of existing *-mingw and aarch64-* stuff...=