From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) by sourceware.org (Postfix) with ESMTPS id 2C6093858036 for ; Wed, 6 Jan 2021 17:28:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 2C6093858036 Received: by mail-wm1-x32a.google.com with SMTP id q75so3298508wme.2 for ; Wed, 06 Jan 2021 09:28:16 -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=QJZ6ldwvZEnBm2k4aCuHWymr/VMlT2ONBcF19Yl/p54=; b=aDVW8z3H+eW6JwhTz15snFz+Gt/TyNiQrZc9ivsjptxMuxVpvgC6cegdA+E+BbkUTg OA9vQ1RnX/o+U6QbQ9jUHt4M7V1Zkm3YuiFXFlP7mJE47aFfdreeeu0U+kN36nEYnRCp 1eSrMebBARMou36u97jQ44+zTTXqZ5vslyaGwPjMJBZShVDs5f1DVT/vgW89FlVeRo5O XsKiBpb79Nmm+27rM6euZyuZ7LPMHcJ9IMFRYWtOASV7y2Iy7X+PjxgAXdc1NtRNTySP yPGIwvzYxQjEymGQZA8UFFHBDFC+2akHFbV3s+MDzi/fokE7mmFRuEqLk/gKl6vkNwUw e/Yw== X-Gm-Message-State: AOAM532SU5Chm2yGFrUvOl6y6g2W7ENAfGr1nRKMG0SUSS7f/jOao1Xg E4d5uFxeP1L8XdxdcK02Umc= X-Google-Smtp-Source: ABdhPJxXBS+wUlavwkF4lhPh5toEriGjLc75pAafujdAPdK1fUj6uKP3Wwx8pUyyI2uUqbC3jJYMvA== X-Received: by 2002:a1c:b4c4:: with SMTP id d187mr4554357wmf.38.1609954095022; Wed, 06 Jan 2021 09:28:15 -0800 (PST) Received: from [192.168.1.212] (host81-138-1-83.in-addr.btopenworld.com. [81.138.1.83]) by smtp.googlemail.com with ESMTPSA id c7sm4428668wro.16.2021.01.06.09.28.13 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jan 2021 09:28:14 -0800 (PST) Content-Type: text/plain; charset=utf-8; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: apple silicon fortran From: Iain Sandoe In-Reply-To: Date: Wed, 6 Jan 2021 17:28:12 +0000 Cc: Rosemary Mardling , Fortran List Content-Transfer-Encoding: 8bit Message-Id: References: <941045F7-9782-408B-BF5A-015E2FAF246A@monash.edu> To: James Secan X-Mailer: Apple Mail (2.3273) X-Spam-Status: No, score=-3.4 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 17:28:17 -0000 James Secan wrote: > Not having had a need to track the gfortran compiler at this level of > detail in the past, I’ve got two questions: > > 1. What’s the nominal timing for gcc releases? From 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? Yes, that’s about right. ---- 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). — in this case, because the relative schedule of the OS and compiler release are so unfortunately out of phase, I’m trying to think of suitable work-arounds (something more official than my github anyway!). > 2. Once there is a release that supports Apple’s 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? Prior to release: the referenced github branch below, and the “homebrew” and “macports” 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 ) … as for issues, the known ones are described here : https://github.com/iains/gcc-darwin-arm64/issues ==== Once support is in a released GCC version: 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 ‘default’ - but, perhaps in handling IEEE stuff and in the REAL*16). >> Rosemary Mardling via Fortran wrote: >> >>> 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? >> >> see : >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168 >> and : >> https://github.com/iains/gcc-darwin-arm64 >> >> It’s (very) experimental at present - but … I believe that both macports >> and homebrew have packages based off this work. >> >> macOS (Darwin) support is on a volunteer basis, so time is limited - we >> will do our best (but it’s more likely to be ‘official’ in GCC 12 than >> 11). cheers Iain