From: Jerry DeLisle <jvdelisle2@gmail.com>
To: James Secan <james.secan@gmail.com>,
Iain Sandoe <idsandoe@googlemail.com>
Cc: Fortran List <fortran@gcc.gnu.org>,
Rosemary Mardling <rosemary.mardling@monash.edu>
Subject: Re: apple silicon fortran
Date: Thu, 7 Jan 2021 18:32:11 -0800 [thread overview]
Message-ID: <caee965d-7e5c-38d5-f8f9-f6827d10b9f6@gmail.com> (raw)
In-Reply-To: <7FCF49F0-EA95-44F1-B5B6-01393378783E@gmail.com>
On 1/6/21 11:38 AM, James Secan via Fortran wrote:
> Thanks - I had already begun to suspect I’ll need to hold off a bit on getting an Apple Silicon machine, and this confirms it. I need gfortran to be working on whatever hardware I’m using.
>
> Jim
>
That may be the wise approach. Depending on how many users it may be
possible to get an unoffcial build if the branch gets far enough a
long. There was a time when we were doing daily or weekly builds for
odd ducks like Cygwin on Windows. This was back at the initial phases
of the F95 compiler.
One of the big problems is not having hardware for us to test on. I
expect Iain and some the gcc other gcc gurus may have this access sooner
than the "Fortraners". If the OS is fairly compliant to standards, the
runtime libraries for gfortran should mostly work, its the nuances and
corner cases that catch us off guard usually.
It would be helpful if we somehow could get an apple on silicon machine
tied into the gcc compile farm. I do not know how well that would work
if it is only laptops, it would be on 24/7, but I expect it could
support a few users well enough to allow developers to start working
with it and seeing the problems.
Another thought, is there some sort of virtual machine or emulator that
could be used on other machines, but apple is usually very closed about
such things.
Regards,
Jerry
next prev parent reply other threads:[~2021-01-08 2:32 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 [this message]
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=caee965d-7e5c-38d5-f8f9-f6827d10b9f6@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=idsandoe@googlemail.com \
--cc=james.secan@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).