From: Iain Sandoe <iain@sandoe.co.uk>
To: "Lingadahally,
Vishakha (2023)" <Vishakha.Lingadahally.2023@live.rhul.ac.uk>
Cc: GCC Fortran <fortran@gcc.gnu.org>
Subject: Re: gfortran: error: unrecognized argument in option '-mcmodel=medium'
Date: Wed, 27 Sep 2023 08:35:42 +0100 [thread overview]
Message-ID: <9572854C-DE41-4B6E-BF4A-4F60B82BF70E@sandoe.co.uk> (raw)
In-Reply-To: <D63B7D76-7B42-4F01-9D4F-9A1735240519@sandoe.co.uk>
> On 27 Sep 2023, at 08:33, Iain Sandoe <iain@sandoe.co.uk> wrote:
>
>
>
>> On 27 Sep 2023, at 08:25, Andrew Pinski via Fortran <fortran@gcc.gnu.org> wrote:
>>
>> On Tue, Sep 26, 2023 at 11:39 PM Richard Biener via Fortran
>> <fortran@gcc.gnu.org> wrote:
>>>
>>> On Tue, Sep 26, 2023 at 4:44 PM Lingadahally, Vishakha (2023)
>>> <Vishakha.Lingadahally.2023@live.rhul.ac.uk> wrote:
>>>>
>>>> Dear GCC Team,
>>>>
>>>> I'm running Ubuntu 22 on my Mac virtually and my gfortran version is 11.4.0. When I try to install a certain software package, I encounter the following error:
>>>>
>>>> gfortran: error: unrecognized argument in option '-mcmodel=medium'
>>>> gfortran: note: valid arguments to '-mcmodel=' are: large small tiny
>>>>
>>>> Is this due to attempting to run gfortran on arm64 architecture? Could you please let me know how I could resolve the issue?
>>>
>>> You have to turn to Ubuntu here, -mcmodel=medium is certainly
>>> supported in GCC 11, maybe Ubuntu patches out
>>> the support?
>>
>> Well -mcmodel=medium is the x86_64 specific option while they are
>> trying to run on aarch64 which has a different set options.
>
>
> The current Arm64 port (aarch64 on macOS) only supports the “small” mcmodel
> “tiny” is not supported by macOS and we have not yet implemented “large”.
>
> Despite it’s name “small” should suffice as an approximate equivalent for the
> x86_64 “medium” (at least on macOS).
>
> So, either you need to change the flag depending on the architecture, or omit it
> (on macOS currently GCC only supports the default mcmodel).
>
> We plan to support the “large” model at some stage on Arm64 (but unlikely for
> GCC 14)
Ah, and now I see you are not running native so the comments above are not
relevant.
Iain
next prev parent reply other threads:[~2023-09-27 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 14:44 Lingadahally, Vishakha (2023)
2023-09-27 6:37 ` Richard Biener
2023-09-27 7:25 ` Andrew Pinski
2023-09-27 7:33 ` Iain Sandoe
2023-09-27 7:35 ` Iain Sandoe [this message]
2023-09-28 13:56 ` [EXT] " Lingadahally, Vishakha (2023)
2023-09-28 16:00 ` [EXT] " Iain Sandoe
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=9572854C-DE41-4B6E-BF4A-4F60B82BF70E@sandoe.co.uk \
--to=iain@sandoe.co.uk \
--cc=Vishakha.Lingadahally.2023@live.rhul.ac.uk \
--cc=fortran@gcc.gnu.org \
/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).