public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <bug-96168-4-6DWKAbqDcY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96168-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168 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 about 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 able to pick up a small piece. Perhaps we can subdivide the work and prioritize what'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 compiler, which is blocking a lot of the scientific computing stack. I think identifying a minimal "fortran-complete" path would be helpful and encourage people to help out :).
next prev parent reply other threads:[~2020-07-11 23:40 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-11 16:32 [Bug bootstrap/96168] New: Cannot bootstrap with Xcode 12 Beta on aarch64, macOS 11.0/Darwin, Apple Silicon gcczilla at cpellegrino dot de 2020-07-11 16:39 ` [Bug bootstrap/96168] " gcczilla at cpellegrino dot de 2020-07-11 16:40 ` pinskia at gcc dot gnu.org 2020-07-11 16:42 ` pinskia at gcc dot gnu.org 2020-07-11 16:50 ` gcczilla at cpellegrino dot de 2020-07-11 20:19 ` egallager at gcc dot gnu.org 2020-07-11 20:56 ` [Bug bootstrap/96168] GCC support for Apple Silicon (Arm64) on macOS requested iains at gcc dot gnu.org 2020-07-11 21:40 ` [Bug target/96168] " gcczilla at cpellegrino dot de 2020-07-11 23:40 ` keno at juliacomputing dot com [this message] 2020-07-12 0:48 ` pinskia at gcc dot gnu.org 2020-08-18 6:45 ` tkoenig at gcc dot gnu.org 2020-08-18 7:47 ` iains at gcc dot gnu.org 2021-04-26 18:19 ` noloader at gmail dot com 2021-11-05 23:18 ` timturnerc at yahoo dot com 2023-02-20 17:41 ` iains at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-96168-4-6DWKAbqDcY@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).