public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <idsandoe@googlemail.com>
To: James Secan <james.secan@gmail.com>
Cc: Jerry DeLisle <jvdelisle2@gmail.com>,
	Fortran List <fortran@gcc.gnu.org>,
	Rosemary Mardling <rosemary.mardling@monash.edu>
Subject: Re: apple silicon fortran
Date: Fri, 8 Jan 2021 19:57:16 +0000	[thread overview]
Message-ID: <CC13D34A-996E-4AFF-A706-6ED0F250901E@googlemail.com> (raw)
In-Reply-To: <7CF99DAF-4600-4A62-9363-DC59B2867A16@gmail.com>

Hi Jim,

James Secan via Fortran <fortran@gcc.gnu.org> wrote:

>> 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,

Yes, I was talking about Arm64/aarch64/Apple Si native/self-hosted on macOS  
11 (Big Sur)

> or on Big Sur on Intel silicon?

macOS 11 on Intel x86_64 will be supported in GCC11 (in fact, is already  
supported and in respectable condition for this stage of the development  
cycle - see [1]); that would be expected to release to the same standard as  
macOS 10.15 (Catalina).

Actually, for the record, there’s a third permutation [2] , but I’ve not  
personally evaluated it.

=====

As for self-hosted, Arm64 native macOS11 ….

> Have the ABI changes you mention been implemented on the back end?

Enough of them have been addressed to be able to bootstrap the compiler and  
get reasonable test output (for Fortran, anyway), but several challenges  
remain…

> That to me seems like the big issue here.

… that is why the branches are described as “experimental”, they certainly  
have limitations (as listed in the issues), but are available to people  
wanting to experiment.

====

I fully understand the need for stability in production platforms (  
although we are of course obliged to develop and test on the ‘bleeding  
edge’  - my production machines stay well away from it too ;) )

cheers
Iain

---

[1] https://gcc.gnu.org/pipermail/gcc-testresults/2021-January/643049.html

---

[2] In principle, an X86_64 compiler can be executed on Arm64 macOS 11  
using “Rosetta 2”.  I haven’t tried this to see how well it works (perhaps  
I will give it a try at some point, both in terms of function and  
performance).


  reply	other threads:[~2021-01-08 19:57 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
2021-01-08 19:57                 ` Iain Sandoe [this message]
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=CC13D34A-996E-4AFF-A706-6ED0F250901E@googlemail.com \
    --to=idsandoe@googlemail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=james.secan@gmail.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).