public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Secan <james.secan@gmail.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: Rosemary Mardling <rosemary.mardling@monash.edu>,
	Fortran List <fortran@gcc.gnu.org>
Subject: Re: apple silicon fortran
Date: Wed, 6 Jan 2021 09:11:01 -0800	[thread overview]
Message-ID: <EC246D80-B701-4C06-BD23-B884EA977634@gmail.com> (raw)
In-Reply-To: <BA186CC7-32F4-430F-AE25-8BBCFA888283@googlemail.com>

Not having had a need to track the gfortran compiler at this level of detail in the past, I’ve got two questions:

1.  What’s the nominal timing for gcc releases?  From looking at recent history it looks to me like gcc 11 will show up in a few months and gcc 12 in Spring 2022.  Is this about right?

2.  Once there is a release that supports Apple’s ARM chips where (if anywhere) would I be able to find a list of things either not yet implemented in gfortran or implemented-but-funky?

And thanks for all the work you’re doing on this.

Jim Secan
Seattle, WA

> On Jan 6, 2021, at 12:53 AM, Iain Sandoe via Fortran <fortran@gcc.gnu.org> wrote:
> 
> Hi Rosemary,
> 
> Rosemary Mardling via Fortran <fortran@gcc.gnu.org> wrote:
> 
>> I am keen to buy the new Apple Macbook Air which uses their new M1 chip, but as yet there is no Fortran compiler.
>> Do you have plans for a compiler for this new chip?
> 
> see :
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168
> and :
> https://github.com/iains/gcc-darwin-arm64
> 
> It’s (very) experimental at present - but … I believe that both macports and homebrew have packages based off this work.
> 
> macOS (Darwin) support is on a volunteer basis, so time is limited - we will do our best (but it’s more likely to be ‘official’ in GCC 12 than 11).
> 
> cheers
> Iain
> 


  reply	other threads:[~2021-01-06 17:11 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 [this message]
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
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=EC246D80-B701-4C06-BD23-B884EA977634@gmail.com \
    --to=james.secan@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=idsandoe@googlemail.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).