From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web10.67539.1680521447336036510 for ; Mon, 03 Apr 2023 04:30:47 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=IG1lMB4t; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680521446; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=qmOxprrojDMlKebHz5oRDTHufygww40Vg1vj7ybcZ8M=; b=IG1lMB4tuxRyZze7fkcfOCiUpAsH2k9SkonLbQW0lQMvvugG07Wih+HE4o1Wg8cOzpRmOz KHTOq20eDiIoeCmCOLrs81UeD6PAZb8PxW57joaJf6RVpBmIdCnhK6V5xrJpWGWbBWOiZr l9Uo2v1Dxw/jr3H65matKYfSWudZssY= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-278-N2wNfcksP1GJyXgAKL1Zbw-1; Mon, 03 Apr 2023 07:30:35 -0400 X-MC-Unique: N2wNfcksP1GJyXgAKL1Zbw-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 8A8E6101A54F; Mon, 3 Apr 2023 11:30:34 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.193.241]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2ED6B2027040; Mon, 3 Apr 2023 11:30:31 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id C3FA51800393; Mon, 3 Apr 2023 13:30:29 +0200 (CEST) Date: Mon, 3 Apr 2023 13:30:29 +0200 From: "Gerd Hoffmann" To: Rebecca Cran Cc: Pedro Falcato , devel@edk2.groups.io, gaoliming , Oliver Smith-Denny , Guomin Jiang , Xiaoyu Lu , Jian J Wang , Jiewen Yao , Ard Biesheuvel , Jordan Justen , Bob Feng , Andrew Fish , Leif Lindholm , Michael D Kinney Subject: =?UTF-8?B?UmU6IOWbnuWkjTogW2VkazItZGV2ZWxdIFtQQVRDSCB2MiAwMC8xM10gQmFzZVRvb2xzLENyeXB0b1BrZyxNZGVQa2csT3ZtZlBrZzogRGVsZXRlIENMQU5HMzUsQ0xBTkczOCxHQ0M0OCxHQ0M0OSwgcmVuYW1lIEdDQzUgdG8gR0NDLCB1cGRhdGUgQ0xBTkdEV0FSRiwgZGVsZXRlIFZTIDIwMDgtMjAxMywgRUJD?= Message-ID: References: <20230328173111.759017-1-rebecca@bsdio.com> <02fb01d961dc$88d6acd0$9a840670$@byosoft.com.cn> <92a85636-3875-fd4d-06ff-dab9670370a5@bsdio.com> MIME-Version: 1.0 In-Reply-To: <92a85636-3875-fd4d-06ff-dab9670370a5@bsdio.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Apr 02, 2023 at 03:50:33PM -0600, Rebecca Cran wrote: > On 4/2/23 12:38 PM, Pedro Falcato wrote: > > As expressed off-list on UEFI talkbox, I like GCCNOLTO, but I would > > rather keep GCC5 as GCC5, for the next future iteration of "lets bump > > a new toolchain because we need feature X". > > Given we've gone from GCC 5 through 12 with no new toolchains, I'd prefer to > just have GCC. > > > This is unsurprising, plenty of NOLTO build breakage. Since no one > > seems to use this, could we think about axing this or? > > > > Just seems silly to have an extra toolchain (with extra cognitive > > overhead for anyone looking at tools_def) for s/-flto//g > > Since Liming wants to keep it, let's make all the other changes (deleting VS > 2008-2013, CLANG35, CLANG38 etc.) and keep GCCNOLTO and GCC for now. If > nobody fixes the problems with GCCNOLTO, maybe we can revisit dropping it in > a few months? I'm wondering what the point in keeping a known-broken toolchain though. It is apparently unused when nobody noticed the breakage ... take care, Gerd