From: Iain Sandoe <idsandoe@googlemail.com>
To: James Secan <james.secan@gmail.com>
Cc: Jerry DeLisle <jvdelisle@charter.net>,
Thomas Koenig <tkoenig@netcologne.de>,
Fortran List <fortran@gcc.gnu.org>,
Rosemary Mardling <rosemary.mardling@monash.edu>
Subject: Re: apple silicon fortran
Date: Sat, 9 Jan 2021 19:30:53 +0000 [thread overview]
Message-ID: <B48BB153-D142-405C-8640-1FBBC2E55256@googlemail.com> (raw)
In-Reply-To: <291F2ED7-BFF4-4F8C-A902-62231FB75425@gmail.com>
Hi Jim,
James Secan <james.secan@gmail.com> wrote:
>> On Jan 9, 2021, at 11:07 AM, Iain Sandoe via Fortran
>> <fortran@gcc.gnu.org> wrote:
>> I am testing out the Rosetta 2 alternative (which is, AFAIU, a
>> binary-conversion done at install-time native on macOS).
>>
>> Useful to have some fall-back solutions in the short-term, but a native
>> compiler is still the eventual objective.
>
> I would think that running the compiler under Rosetta 2 would still
> produce a binary that is not compatible with the M1 processor (would it
> run on a Mac Intel box?).
Yes, that’s right - it would be an x86_64 compiler, running via Rosetta on
Arm64, producing X86_64 object ...
> Can you run the binary on M1 using Rosetta 2 again?
… it would seem to defeat some use-case if not - given that the bootstrap
succeeded, evidently yes (but perhaps using the JIT mechanism, which might
not perform so well)..
> And my admittedly-shallow understanding of Rosetta 2, isn’t it supposed
> to generate a new binary the first time a code is run using it, said new
> binary then being run directly in a subsequent invocation of
> Rosetta2+userApp?
Actually, (from limited reading, and likely equally shallow understaning),
it seems that this operates two ways; a one-off when something is
installed (so that from then-on one is running native code, with no
translation phase). That’s different from the Rosetta 1 (PowerPC=>X86).
The second mode is more akin to the Rosetta 1 case, a JIT that is run as
needed...
> I am interested to hear the results of your testing with Rosetta 2.
I bootstrapped x86_64-apple-darwin20 on aarch64-darwin20.3, and currently
running the Fortran testsuite - it’s not clear to me if some of the issues
(PIE and no-executable stack) will be sidestepped or not. We shall see.
Iain
next prev parent reply other threads:[~2021-01-09 19:30 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
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 [this message]
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=B48BB153-D142-405C-8640-1FBBC2E55256@googlemail.com \
--to=idsandoe@googlemail.com \
--cc=fortran@gcc.gnu.org \
--cc=james.secan@gmail.com \
--cc=jvdelisle@charter.net \
--cc=rosemary.mardling@monash.edu \
--cc=tkoenig@netcologne.de \
/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).