From: James Secan <james.secan@gmail.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: Rosemary Mardling <rosemary.mardling@monash.edu>,
Jerry DeLisle <jvdelisle2@gmail.com>,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: apple silicon fortran
Date: Fri, 8 Jan 2021 11:28:54 -0800 [thread overview]
Message-ID: <7CF99DAF-4600-4A62-9363-DC59B2867A16@gmail.com> (raw)
In-Reply-To: <707CA4B6-DAAE-4DA6-A954-1E3ADE0CDA6B@googlemail.com>
> On Jan 8, 2021, at 1:56 AM, Iain Sandoe <idsandoe@googlemail.com> wrote:
>
> In fact, none of the issues Jerry mentions are really the blockers:
> - you can already get builds of the experimental branch from homebrew and macports
> - ( and I would surely be willing to release mine, which are generally weekly, if someone has a suitable hosting site ).
Are these ready to run on Apple silicon, or on Big Sur on Intel silicon? Have the ABI changes you mention been implemented on the back end? That to me seems like the big issue here.
Jim
next prev parent reply other threads:[~2021-01-08 19:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 5:58 Rosemary Mardling
2021-01-06 8:53 ` Iain Sandoe
2021-01-06 17:11 ` James Secan
2021-01-06 17:28 ` Iain Sandoe
2021-01-06 19:38 ` James Secan
2021-01-08 2:32 ` Jerry DeLisle
2021-01-08 3:26 ` Rosemary Mardling
2021-01-08 9:56 ` Iain Sandoe
2021-01-08 10:05 ` Richard Biener
2021-01-08 19:28 ` James Secan [this message]
2021-01-08 19:57 ` Iain Sandoe
2021-01-08 22:18 ` Thomas Koenig
2021-01-09 17:29 ` Jerry DeLisle
2021-01-09 17:37 ` Jerry DeLisle
2021-01-09 19:07 ` Iain Sandoe
2021-01-09 19:21 ` James Secan
2021-01-09 19:30 ` Iain Sandoe
2021-01-12 22:13 ` Iain Sandoe
2021-01-15 20:36 ` James Secan
2021-02-26 22:24 ` Rosemary Mardling
2021-01-09 19:26 ` Jerry DeLisle
2021-01-06 23:26 ` Rosemary Mardling
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=7CF99DAF-4600-4A62-9363-DC59B2867A16@gmail.com \
--to=james.secan@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=idsandoe@googlemail.com \
--cc=jvdelisle2@gmail.com \
--cc=rosemary.mardling@monash.edu \
/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: link
Be 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).