From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mx.groups.io with SMTP id smtpd.web11.55717.1680472237611849046 for ; Sun, 02 Apr 2023 14:50:37 -0700 Authentication-Results: mx.groups.io; dkim=fail reason="signature has expired" header.i=@bsdio.com header.s=fm3 header.b=Egxq0eqC; spf=pass (domain: bsdio.com, ip: 66.111.4.26, mailfrom: rebecca@bsdio.com) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 8204F5C00C5; Sun, 2 Apr 2023 17:50:36 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 02 Apr 2023 17:50:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdio.com; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1680472236; x=1680558636; bh=7brEbuwhPYvLqftnePaT+d1xr5GH2cHrGl5 Sy7wY9cM=; b=Egxq0eqCxM4fgyxISKASDKd+BRzRj7+CNXi8SiOVYvNrcflQnxl ytiefZQwTzYIyLm3oo1/9altSFAbHvcQfntTgeh/Cr3iGPjx+pDYQO6KK2wDIILG iBLowrlcdbroee7lNpBflvjmwleJFjFxEwH7BUfhfWwGHql+FQu4qZlZIxBpMt4Z ErXCT83y30Xvmxf51gM3khxJmoDA5KD1Oe4DRSFlNh8vSsqoPa5rCdJh9aYotR5x haX4jkEdZHSKgF3TVcw87EtDi9sLcwKfbE6UifFP0gHOVuEmBibtw3PLlgHJ38fB bjLgPYaRZmgI9j0MBm7M6sIslEjgDKzirOg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1680472236; x=1680558636; bh=7brEbuwhPYvLqftnePaT+d1xr5GH2cHrGl5 Sy7wY9cM=; b=Yojz4W3X/AM/Lq+RTa3oGrlRpWcdJBAIZ3OmVoSCPcToixJEkYO qoXcIaXnSXx1E2K/mb1+uJSHrxv4qYA1V8SPHutUhuUZzYyrpc0YNkPNs1om1pgz bJAnTD7F1Peq+Vus0bBKelS+WMyX45xwNbDPBqxrSFkOKRTRK59X1VOecgbCdE6t /rAs4jVfGRmoQ2fUC6mQYIZRmV9r2xcVHAIHjsGDTO2kxsKVGO7qc5ixGHDxbhRn 7BEOL4wnxCLzGm0KE3xZnpiThZ77zyrWT7aOtDLQLxIXYwytqjR8jwLjKU73ffXd cndruALTcWGag/oQCsFBZ1Oq+ZP8uUlRCGQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdeiiedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeftvggs vggttggrucevrhgrnhcuoehrvggsvggttggrsegsshguihhordgtohhmqeenucggtffrrg htthgvrhhnpeehleekgfdutedugeehgeffgffhteefhffhteetfeevhefgvdejhedthfff ieffleenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hrvggsvggttggrsegsshguihhordgtohhm X-ME-Proxy: Feedback-ID: i5b994698:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 2 Apr 2023 17:50:34 -0400 (EDT) Message-ID: <92a85636-3875-fd4d-06ff-dab9670370a5@bsdio.com> Date: Sun, 2 Apr 2023 15:50:33 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: =?UTF-8?B?UmU6IOWbnuWkjTogW2VkazItZGV2ZWxdIFtQQVRDSCB2MiAwMC8xM10gQmFzZVRvb2xzLENyeXB0b1BrZyxNZGVQa2csT3ZtZlBrZzogRGVsZXRlIENMQU5HMzUsQ0xBTkczOCxHQ0M0OCxHQ0M0OSwgcmVuYW1lIEdDQzUgdG8gR0NDLCB1cGRhdGUgQ0xBTkdEV0FSRiwgZGVsZXRlIFZTIDIwMDgtMjAxMywgRUJD?= To: Pedro Falcato , devel@edk2.groups.io Cc: gaoliming , Oliver Smith-Denny , Guomin Jiang , Xiaoyu Lu , Jian J Wang , Jiewen Yao , Ard Biesheuvel , Jordan Justen , Gerd Hoffmann , Bob Feng , Andrew Fish , Leif Lindholm , Michael D Kinney References: <20230328173111.759017-1-rebecca@bsdio.com> <02fb01d961dc$88d6acd0$9a840670$@byosoft.com.cn> From: "Rebecca Cran" In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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? -- Rebecca Cran