From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) by mx.groups.io with SMTP id smtpd.web11.47442.1680450111869773201 for ; Sun, 02 Apr 2023 08:41:52 -0700 Authentication-Results: mx.groups.io; dkim=fail reason="signature has expired" header.i=@bsdio.com header.s=fm3 header.b=RJo47jrt; spf=pass (domain: bsdio.com, ip: 64.147.123.19, mailfrom: rebecca@bsdio.com) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id C574232000E5; Sun, 2 Apr 2023 11:41:49 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 02 Apr 2023 11:41:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdio.com; h=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= 1680450109; x=1680536509; bh=kunMKip12JqHpn2B2z/JkzjK7a3tqR2yNpi nTQYyUg0=; b=RJo47jrtao4nJGyLRWjSrF2Qd24eobvB4n187ISZw8ncg0J4thN 2mgxbiOexor2SKU9OvycGXA2OQJaPeNctnmyg0dUk5YtxTbrrb2h4mEVrsZRUVxd Z7UXrVJnOqoj7Y7fE22VPetOB1g95/BDOxmpLWF5ZWnAL+ob3GgKnX++zKim3Yfi eZAsUx+9mkFqcMwmbSCcrAaOblc5QLRr3tZCyRF9/Mh7u44M09q+jxLTxSvDf8Es /xlgt7S43+70VTvzNu3IqmJ8ymWGm4f5+LulPj0cu8xXfsNxbD5gs/k33R9yKsfw 6ZEwVDneWyldK6+Nd3fRSd9n5DvrTk8D3Ow== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=1680450109; x= 1680536509; bh=kunMKip12JqHpn2B2z/JkzjK7a3tqR2yNpinTQYyUg0=; b=o RoGcKqSQhiaMSNtAZ0CBVZzHins1QhLrQRtjUpSH8+DqHfEQNq3zpSAm1zbrVDtM CcMXp4v3hgFCgbe+9yZh25bF52yLePUDSy2R2T3nehmXJnNZ+mCML3gz1clEborG pykOvZjpvA7MczssRBNBhK8y5SGdZkmmqN0pePK3FqJgHnoYJ/dyzPTl/vPySIg7 PmL12rHRjyzcf0L0r/WNmeyeibFgYzWV3hFiXdJ3URo2hsIySm6mm/mXmnfWtcFm jsUNY4NRMfe77CmizIXthNetD13jSLNGTbb7ETnAnIu15Qegil+lN0fFV2fgn1+I Iq2r+Dla0AtFgppI1VEqw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdeihedgledvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomheptfgvsggv tggtrgcuvehrrghnuceorhgvsggvtggtrgessghsughiohdrtghomheqnecuggftrfgrth htvghrnhepueehffegfeeluedufefffeejieeugeegvdefgffhueetheeuheegieeftddu feehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprh gvsggvtggtrgessghsughiohdrtghomh X-ME-Proxy: Feedback-ID: i5b994698:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 2 Apr 2023 11:41:47 -0400 (EDT) Message-ID: Date: Sun, 2 Apr 2023 09:41:46 -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: gaoliming , devel@edk2.groups.io, '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: <02fb01d961dc$88d6acd0$9a840670$@byosoft.com.cn> Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 3/28/23 7:19 PM, gaoliming wrote: > GCC49 is one GCC tool chain without LTO enable option. GCC5 is another GCC tool chain with LTO enable option. > > They have the different usage. I suggest to keep GCC49 and GCC5 both, and also keep their name as is. Is anything still _using_ GCC49 though? Since I strongly suspect nobody is using gcc 4.9, I'll rename it to GCCNOLTO. When I try and build OVMF with it, I get the following error: /UefiShellDebug1CommandsLib/SmbiosView/PrintInfo.c /home/bcran/src/uefi/edk2/OvmfPkg/Library/BaseMemEncryptSevLib/X64/SnpPageStateChangeInternal.c: In function ‘InternalSetPageState’: /home/bcran/src/uefi/edk2/OvmfPkg/Library/BaseMemEncryptSevLib/X64/SnpPageStateChangeInternal.c:166:37: error: ‘Cmd’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   166 |     Info->Entry[i].CurrentPage      = 0;       |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~ /home/bcran/src/uefi/edk2/OvmfPkg/Library/BaseMemEncryptSevLib/X64/SnpPageStateChangeInternal.c:32:10: note: ‘Cmd’ was declared here    32 |   UINTN  Cmd;       |          ^~~ rm -f /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_GCC49/X64/NetworkPkg/Library/DxeIpIoLib/DxeIpIoLib/OUTPUT/DxeIpIoLib.lib "ar" cr /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_GCC49/X64/NetworkPkg/Library/DxeIpIoLib/DxeIpIoLib/OUTPUT/DxeIpIoLib.lib @/home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_GCC49/X64/NetworkPkg/Library/DxeIpIoLib/DxeIpIoLib/OUTPUT/object_files.lst cc1: all warnings being treated as errors make: *** [GNUmakefile:304: /home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_GCC49/X64/OvmfPkg/Library/BaseMemEncryptSevLib/PeiMemEncryptSevLib/OUTPUT/X64/SnpPageStateChangeInternal.obj] Error 1 build.py...  : error 7000: Failed to execute command     make tbuild [/home/bcran/src/uefi/edk2/Build/OvmfX64/RELEASE_GCC49/X64/OvmfPkg/Library/BaseMemEncryptSevLib/PeiMemEncryptSevLib] build.py...  : error F002: Failed to build module  /home/bcran/src/uefi/edk2/OvmfPkg/Library/BaseMemEncryptSevLib/PeiMemEncryptSevLib.inf [X64, GCC49, RELEASE] - Failed - Build end time: 09:38:34, Apr.02 2023 Build total time: 00:00:14 -- Rebecca Cran