From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) by sourceware.org (Postfix) with ESMTPS id A8EF23850410 for ; Wed, 6 Jan 2021 19:38:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A8EF23850410 Received: by mail-pf1-x42e.google.com with SMTP id w6so2311541pfu.1 for ; Wed, 06 Jan 2021 11:38:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=AawIR7HovbyXNXx7Hrn3KDYwYmf2s1G6lVBmsyV5YmY=; b=k8u10ktx5OCuvPaX4I2BRgGKFPZ2EOjJD9QOZbSmpvHOXphhmA7W+VNOMVPLSX5cnX EZIUjfOq9O/W3QhLs4PPEMlt+vEuAy8yv09RPxCIWDOIdFgiEt7oiBTd/R0twgMZIGAG uXy8gdMvlEz/ir8KA4Wwxijhwjco1zQz4Bpuwiz5+Lb9N5taZSyrH0g01LWPth9CRzU5 DzfwJPTgLyAzDYFC6e6Kj9SyTQrzmJabomB+3wVLKU6wKa12050Xsqxnf2DdiSCytxBH kKGnGxgT1mKrbs4pXnOYBEYTnn/upIy+pIID1by1OPvX7V+ah6zQ/hmgJ8yF7zJdOqdJ nZUw== X-Gm-Message-State: AOAM530UksYLy7Ffy/1oNz4dlXpBtOsqT0wIYlr1OkfqrKjCIKh41p0v N3txB/aIbUsVTwP/XcF3AWg= X-Google-Smtp-Source: ABdhPJyjojvDh5izS+nbXUCkU+x7eQsO1uNJA/J46twTCailOX8O923WKnxBzxcFTPmd2T3wIHlypg== X-Received: by 2002:a63:5f12:: with SMTP id t18mr6165028pgb.308.1609961897807; Wed, 06 Jan 2021 11:38:17 -0800 (PST) Received: from [192.168.6.101] (c-71-197-179-6.hsd1.wa.comcast.net. [71.197.179.6]) by smtp.gmail.com with ESMTPSA id k14sm3262234pfp.132.2021.01.06.11.38.17 (version=TLS1 cipher=ECDHE-ECDSA-AES128-SHA bits=128/128); Wed, 06 Jan 2021 11:38:17 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: apple silicon fortran From: James Secan In-Reply-To: Date: Wed, 6 Jan 2021 11:38:16 -0800 Cc: Rosemary Mardling , Fortran List Content-Transfer-Encoding: quoted-printable Message-Id: <7FCF49F0-EA95-44F1-B5B6-01393378783E@gmail.com> References: <941045F7-9782-408B-BF5A-015E2FAF246A@monash.edu> To: Iain Sandoe X-Mailer: Apple Mail (2.3124) X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: fortran@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Fortran mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jan 2021 19:38:20 -0000 Thanks - I had already begun to suspect I=E2=80=99ll 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=E2=80=99m using. Jim > On Jan 6, 2021, at 9:28 AM, Iain Sandoe = wrote: >=20 > James Secan wrote: >=20 >> Not having had a need to track the gfortran compiler at this level of = detail in the past, I=E2=80=99ve got two questions: >>=20 >> 1. What=E2=80=99s the nominal timing for gcc releases? =46rom = 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? >=20 > Yes, that=E2=80=99s about right. >=20 > ---- >=20 > This is an odd case, in that the OS [macOS 11 + Arm64 changes] release = happened almost exactly at the same time as we closed GCC11 for new = features. Having said that, new ports have a bit more lattitude (but I = am far from confident that we could get sufficient polish on this one to = have it in 11). >=20 > =E2=80=94 in this case, because the relative schedule of the OS and = compiler release are so unfortunately out of phase, I=E2=80=99m trying = to think of suitable work-arounds (something more official than my = github anyway!). >=20 >> 2. Once there is a release that supports Apple=E2=80=99s 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? >=20 > Prior to release: >=20 > the referenced github branch below, and the =E2=80=9Chomebrew=E2=80=9D = and =E2=80=9Cmacports=E2=80=9D distributions based off it (homebrew, in = fact, uses a backport of the changes to GCC-10 stable branch ( a branch = on https://github.com/fxcoudert/gcc ) >=20 > =E2=80=A6 as for issues, the known ones are described here : >=20 > https://github.com/iains/gcc-darwin-arm64/issues >=20 > =3D=3D=3D=3D >=20 > Once support is in a released GCC version: >=20 > Then the [GCC] release documentation and the GCC bugzilla would = contain the information > (one would not expect there to be too many departures from the = =E2=80=98default=E2=80=99 - but, perhaps in handling IEEE stuff and in = the REAL*16). >=20 >>> Rosemary Mardling via Fortran wrote: >>>=20 >>>> 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? >>>=20 >>> see : >>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96168 >>> and : >>> https://github.com/iains/gcc-darwin-arm64 >>>=20 >>> It=E2=80=99s (very) experimental at present - but =E2=80=A6 I = believe that both macports and homebrew have packages based off this = work. >>>=20 >>> macOS (Darwin) support is on a volunteer basis, so time is limited - = we will do our best (but it=E2=80=99s more likely to be =E2=80=98official=E2= =80=99 in GCC 12 than 11). >=20 > cheers > Iain >=20 >=20