public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: Rosemary Mardling <rosemary.mardling@monash.edu>,
	Jerry DeLisle <jvdelisle2@gmail.com>
Cc: Fortran List <fortran@gcc.gnu.org>,
	Iain Sandoe <idsandoe@googlemail.com>
Subject: Re: apple silicon fortran
Date: Fri, 8 Jan 2021 23:18:08 +0100	[thread overview]
Message-ID: <a0c44efe-e466-35f4-98b7-7b2b26e6d4df@netcologne.de> (raw)
In-Reply-To: <E44A1462-FE41-4F51-AB24-A107200E747D@monash.edu>

Hi Rosemary,

> It seems NAG have a fortran compiler but it is quite expensive (GBP250 - I enquired):
> 
> https://www.nag.com/news/first-fortran-compiler-apple-silicon-macs

Well, NAG sort of cheat - they compile Fortran to C and then use the
native C compiler.  Makes it easier if there is already a C compiler
on the target, no need to worry about ABIs and such.  (Interestingly
enough, the whole NAG compiler has a similar scope as the gfortran
front end and library).

It would be interesteing to see the C code they emit for certain
constructs, for example for code accessing variables in an outer
scope from contained procedures. Not sure if there is an option to
do this.

Best regards

	Thomas

  parent reply	other threads:[~2021-01-08 22:18 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
2021-01-08 22:18             ` Thomas Koenig [this message]
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=a0c44efe-e466-35f4-98b7-7b2b26e6d4df@netcologne.de \
    --to=tkoenig@netcologne.de \
    --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).