From: "Lendacky, Thomas" <thomas.lendacky@amd.com>
To: Rebecca Cran <quic_rcran@quicinc.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Erdem Aktas <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>,
Jiewen Yao <jiewen.yao@intel.com>, Min Xu <min.m.xu@intel.com>,
edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: OvmfPkg VmgExitLib fails to build with CLANG38 (clang 13.0.0)
Date: Wed, 2 Feb 2022 15:16:57 -0600 [thread overview]
Message-ID: <3f4127be-35b1-ec66-25f9-12bdbd5fd0d7@amd.com> (raw)
In-Reply-To: <facfe770-eebf-e5c4-ef6c-5959b4524a01@quicinc.com>
On 2/2/22 14:54, Rebecca Cran wrote:
> VmgExitLib fails to build with the CLANG38 toolset (clang 13.0.0):
>
>
> edk2/OvmfPkg/Library/VmgExitLib/VmgExitVcHandler.c:1875:9: error: variable
> 'Compacted' is used uninitialized whenever 'if' condition is false [-Werror,-W
> sometimes-uninitialized]
> if (EcxIn == 1) {
> ^~~~~~~~~~
> edk2/OvmfPkg/Library/VmgExitLib/VmgExitVcHandler.c:1895:12: note:
> uninitialized use occurs here
> Compacted
> ^~~~~~~~~
> edk2/OvmfPkg/Library/VmgExitLib/VmgExitVcHandler.c:1875:5: note: remove
> the 'if' if its condition is always true
> if (EcxIn == 1) {
> ^~~~~~~~~~~~~~~~
> edk2/OvmfPkg/Library/VmgExitLib/VmgExitVcHandler.c:1871:37: note:
> initialize the variable 'Compacted' to silence this warning
> BOOLEAN Compacted;
> ^
> = '\0'
This looks like the same error that XCODE5 was complaining about. The
patch was submitted by Brijesh, but some CI failure occurred. I'm not sure
how that is possible from a one line patch like that, maybe it has
something to do with the file in general, excluding the patch?
Thanks,
Tom
>
> --
> Rebecca Cran
>
next prev parent reply other threads:[~2022-02-02 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 20:54 OvmfPkg VmgExitLib fails to build with CLANG38 (clang 13.0.0) Rebecca Cran
2022-02-02 21:16 ` Lendacky, Thomas [this message]
2022-02-03 0:16 ` [edk2-devel] " Rebecca Cran
2022-02-04 15:53 ` Brijesh Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f4127be-35b1-ec66-25f9-12bdbd5fd0d7@amd.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox