public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <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: Tue, 18 Aug 2020 07:47:00 +0000 [thread overview] Message-ID: <bug-96168-4-5XcAeaZP67@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 --- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Thomas Koenig from comment #10) > Since there is no other viable Fortran compiler on iOS, AFAIK, iOS has not been supported by GCC since Apple gcc-4.2.1 and the Apple releases didn't have gfortran. this applies to the shift of macOS to arm64. (although, ironically, supporting arm64 GCC on macOS would bring support to iOS too). > this means that packages like R, numpy and anything else will not > work on the new hardware. > > I guess the advice will just have to be: Do not buy any new-style > Macs if you plan to do any scientific work at all until this has > been resolved. https://github.com/iains/gcc-darwin-arm64#readme .. but a volunteer effort and vying for time with every other bug / enhancement.
next prev parent reply other threads:[~2020-08-18 7:47 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 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 [this message] 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-5XcAeaZP67@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).