From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.wavenetuk.net (smtp.wavenetuk.net [195.26.36.10]) by sourceware.org (Postfix) with ESMTP id 1320B385800C for ; Wed, 23 Dec 2020 14:07:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 1320B385800C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=sandoe.co.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=iain@sandoe.co.uk Received: from [192.168.1.212] (host81-138-1-83.in-addr.btopenworld.com [81.138.1.83]) by smtp1.wavenetuk.net (Postfix) with ESMTPA id 1FBE4120149C; Wed, 23 Dec 2020 14:07:34 +0000 (GMT) Content-Type: text/plain; charset=utf-8; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: GCC 10.2 Released From: Iain Sandoe In-Reply-To: Date: Wed, 23 Dec 2020 14:06:50 +0000 Cc: Richard Biener , gcc@gcc.gnu.org, =?utf-8?Q?Martin_Li=C5=A1ka?= Content-Transfer-Encoding: 8bit Message-Id: <091684A6-70AA-4D7D-AF2E-3BA8F25232DD@sandoe.co.uk> References: <1B15717E-D917-4402-B6A1-C0DE6A7B6D0D@gmail.com> To: FX X-Mailer: Apple Mail (2.3273) X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00, KAM_COUK, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_SHORT, KHOP_HELO_FCRDNS, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2020 14:07:36 -0000 FX, Martin Liška wrote: > On 12/23/20 11:49 AM, FX via Gcc wrote: >> Hi all, >> The gcc 10.2 release was 5 months ago today. A lot has happened in the >> gcc-10 branch since, in particular on aarch64. Could a new release be >> issued? It would make efforts at maintaining patches on top of the >> gcc-10 branch easier, in particular in view of the release of >> aarch64-apple-darwin machines. > > Hello. > > I understand your situation, but based on our release schedule, please > expect 10.3 to > be released at the beginning of March 2021, similarly to what we did for > 9.3 and 8.3: > > GCC 9.3 release (2020-03-12) > GCC 8.3 release (2019-02-22) > > as seen here: > https://gcc.gnu.org/develop.html > > Note that making a release consumes some cycles mainly for release > managers. > > Thanks for understanding, [FAOD I am not disagreeing with what you say, I personally have quite a backlog of backports for 10.x, not to mention fixes to make to coroutines that should also be applied there… ] Nevertheless: We have an unusual situation in that we have: - a major OS release that has incompatible numbering with the preceding ones. - a new architecture to support (which will not be ‘official’ in 10.x even if, by some miracle, it’s ready for 11). So I think it might be possible to help the Darwin ‘downstreams’ by making the equivalent of a “vendor” branches for Darwin - in this case [for open branches] based on some arbitrary point in time (e.g. 1.1.2021) rather than on a GCC dot release. For the closed branches that we want to be able to build on Darwin20, the base can be the last dot release. Those branches could live in users/darwin or vendors/darwin .. (we kinda started discussing that on irc one day) - I guess I don’t have a big axe to grind on which [but it’s probably better in one of those, than under my user or on github]. It would be clear that this is Darwin-specific [branch name amended, for example] (i.e. that test coverage was concentrated on the platform). This would not be something I’d want to make a habit of - as Martin says (even for regular maintainers) release cycles chew a lot of time and resources in wider testing. Open to other suggestions, of course, Iain