From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BD3B33857004; Sun, 12 Jul 2020 00:48:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BD3B33857004 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1594514881; bh=rEP0QaNbvi0PJPvMf7yuh1CzPcqj6f6FoCFTWkqGuLE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Si17XJnX/dXnDdqdNIA+Mwvx0GvzLx6v8fHl9yuUarCRmFlzoEGDS1eetZfkT/+EI TpZJ8ixIbYN/AUf1uR0bYaDk66jOCS3YoEHLd5W3mULL01wdeN89tZg4TFgVmiCHYw NXc/MbkffD98ZwV7Z7mDi0fT9/LrZxkz0Xxp5CEQ= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96168] GCC support for Apple Silicon (Arm64) on macOS requested Date: Sun, 12 Jul 2020 00:48:01 +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: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: SUSPENDED 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2020 00:48:01 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96168 --- Comment #9 from Andrew Pinski --- (In reply to Keno Fischer from comment #8) > Is there a list of all the things that need doing? I don't know very much > about how GCC is architected (but am familiar with LLVM,MachO,Aarch64 ISA, > etc), but from my naive point of view, at least >=20 > - Add all the ARM64 MachO relocations GCC does not output macho files directly, so this part is just printing. > - Add special cases for the Aarch64 ABI differences on Apple platforms This one should be the majority of the work really. > - Implement parsing/(& printing?) for Apple's assembly dialect The printing part is part of GCC, GCC has support for alternative dialect t= hat can be used here. > - Add CPU models for the relevant chips You don't need this to start out with really, since ARMv8.3-a is backwards compatiable with ARMv8-a. You could default the arch to armv8.3-a if you w= ant.=