From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) by sourceware.org (Postfix) with ESMTPS id 8286B385781B for ; Sat, 3 Apr 2021 10:34:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8286B385781B Received: by mail-wm1-x32b.google.com with SMTP id n11-20020a05600c4f8bb029010e5cf86347so5865641wmq.1 for ; Sat, 03 Apr 2021 03:34:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JTLawWWGxmoQO2YG/w6dyy96DqrzKt3VElqY3YgMdZM=; b=fta+sz6i1rctoDZXcReW9MZly0kAh58F1aIfDzrRiZxk1AYRayDCHejvWlfOgcg24e X1jX5RCUa6ZZeNhzWBscIOvjqNDUux+jInAmck7oVQ564y1Mqh6nfUtvWWfZ+3c2IQHn 5pR4BqnfqFpxAn0oeIpwEDHtwsLxKVGNpmSRnErE5bl+Q4CmLojIWOKL7cEGxsse/Rbe TOMyrABnBA66GvriFF1j7/9CQyUEVcKFSzfMnpZIdv7RsbCwBfaVJjUMkQLu4zJQyoxI xm591cdWRvfOkcqqKJnPCunrZK2OAlJQh00xdHdrcSatmweuHaYHBntWq5zYu2wCB/87 TLuw== X-Gm-Message-State: AOAM530+E2L80V/SybMPK5z40tCL7kpH/xKbDAaJ95vlpuIJNSpfpt+I SUiXp0l10F07tmoMe7/Hho7wbfNYaHbpk63NzSQ= X-Google-Smtp-Source: ABdhPJykNbci42gB2c7YeS7O9drgxWJQtD3KTDjyzda5yqCPJHQEeZHALxCmMKBWtaD0Utytjv4gnMrRhS3eqBanL2s= X-Received: by 2002:a1c:1b4d:: with SMTP id b74mr1068171wmb.106.1617446078232; Sat, 03 Apr 2021 03:34:38 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Sat, 3 Apr 2021 11:34:26 +0100 Message-ID: Subject: Re: GCC 10.3 Release Candidate available from gcc.gnu.org To: Richard Copley Cc: Richard Biener , "gcc@gcc.gnu.org" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.6 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: 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: Sat, 03 Apr 2021 10:34:41 -0000 On Sat, 3 Apr 2021 at 00:53, Richard Copley via Gcc wrote: > > On 01/04/2021 13:35, Richard Biener wrote: > > The first release candidate for GCC 10.3 is available from > > > > https://gcc.gnu.org/pub/gcc/snapshots/10.3.0-RC-20210401/ > > ftp://gcc.gnu.org/pub/gcc/snapshots/10.3.0-RC-20210401/ > > > > and shortly its mirrors. It has been generated from git commit > > 892024d4af83b258801ff7484bf28f0cf1a1a999. > > > > I have so far bootstrapped and tested the release candidate on > > x86_64-linux. Please test it and report any issues to bugzilla. > > > > If all goes well, I'd like to release 10.3 on Thursday, April 8th. > > > > On Windows, linking two C++ translation units that both #include > results in errors about multiple definition of the weak > function __dummy_resume_destroy. This can be avoided by cherry-picking > commit 94fd05f1f76faca9dc9033b55d44c960155d38e9 [PR 95917]. That problem is already present in GCC 10.2, right? I didn't backport that because it's an ABI change, so not appropriate to change between minor releases (even for an experimental feature like coroutines). PR 95917 was about suboptimal codegen; nobody reported that there's a multiple definition error on Windows. I don't think we should fix this for 10.3, but please report it to bugzilla and we can look into a fix for 10.4 (maybe with something specific to Windows).