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 8469A3857C7D; Sat, 11 Jul 2020 23:40:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8469A3857C7D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1594510817;
 bh=MxauhyDCLz/6T0Yb6I5Q5NwBkRIi79alytdXZ+eQIak=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=JBL3c3MCpiSnJmEGagE/vKZaoI5crEBKDTH8UdJJ+2zbwb2WSr4R2HJPEyBCVxFi3
 lURrjW84pnsQ4TNRdhQHAOVKu04hcaAEUQiRbE0xctmhtUjfVJklHQ6iW+Qle3TkzG
 9DwJQLSBWUOgXXkUdAvlqNL7NHt83cdxNq04Rat0=
From: "keno at juliacomputing dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96168] GCC support for Apple Silicon (Arm64) on macOS
 requested
Date: Sat, 11 Jul 2020 23:40:17 +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: keno at juliacomputing dot com
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: cc
Message-ID: <bug-96168-4-6DWKAbqDcY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-96168-4@http.gcc.gnu.org/bugzilla/>
References: <bug-96168-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Jul 2020 23:40:17 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96168

Keno Fischer <keno at juliacomputing dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |keno at juliacomputing dot=
 com

--- Comment #8 from Keno Fischer <keno at juliacomputing dot com> ---
Is there a list of all the things that need doing? I don't know very much a=
bout
how GCC is architected (but am familiar with LLVM,MachO,Aarch64 ISA, etc), =
but
from my naive point of view, at least

- Add all the ARM64 MachO relocations
- Add special cases for the Aarch64 ABI differences on Apple platforms
- Implement parsing/(& printing?) for Apple's assembly dialect
- Add CPU models for the relevant chips

The good news is that I don't think there's currently any proprietary ISA
extensions that we would have to worry about, so most of the code generation
should just go through.

I unfortunately don't have very much time myself either, but might able abl=
e to
pick up a small piece. Perhaps we can subdivide the work and prioritize wha=
t's
on the "critical path". I think the biggest reason people are clamoring for=
 GCC
support at the moment is that the platform otherwise has no fortran compile=
r,
which is blocking a lot of the scientific computing stack. I think identify=
ing
a minimal "fortran-complete" path would be helpful and encourage people to =
help
out :).=