From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from angie.orcam.me.uk (angie.orcam.me.uk [78.133.224.34]) by sourceware.org (Postfix) with ESMTP id F3C6E3858C00 for ; Tue, 30 May 2023 08:05:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org F3C6E3858C00 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=orcam.me.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=orcam.me.uk Received: by angie.orcam.me.uk (Postfix, from userid 500) id 1874E92009D; Tue, 30 May 2023 10:05:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 1472392009C; Tue, 30 May 2023 09:05:44 +0100 (BST) Date: Tue, 30 May 2023 09:05:43 +0100 (BST) From: "Maciej W. Rozycki" To: Jan-Benedict Glaw cc: =?UTF-8?Q?Marc_Poulhi=C3=A8s?= , Eric Botcazou , gcc-patches@gcc.gnu.org Subject: Re: [COMMITTED] ada: Remove the body of System.Storage_Elements In-Reply-To: <20230529152838.t76qkmqcx4yykobc@lug-owl.de> Message-ID: References: <20230523080826.1873735-1-poulhies@adacore.com> <20230529141023.cj6fyy73zfqdcx4v@lug-owl.de> <87fs7f8bbw.fsf@adacore.com> <20230529152838.t76qkmqcx4yykobc@lug-owl.de> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-1163.2 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_INFOUSMEBIZ,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Mon, 29 May 2023, Jan-Benedict Glaw wrote: > > Can you elaborate how you build GCC? > > My host compileris Debian's "gcc-snapshot", by now some two months > old. (As Eric wrote, it's probably just too old.) That compiler is > given for CC/CXX. The new build is just (as I wrote in the initial > mail) the configure/make call. So I'll just wait for the next drop for > Debian's "gcc-snapshot" package. I see that there are already a good > number of additional commits on the package source, I guess a new > package version is imminent. Alternatively you can just bootstrap GCC under test natively first and then use the newly-built compiler for all the cross builds you want to verify. As you need to do it only once per iteration the extra time spent on the native build shouldn't be a big fraction of the duration of the whole iteration. A drawback is if this native bootstrap fails for any reason, it will make the whole run invalid, i.e. none of the cross targets will be verified. Maciej