From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn
Cc: Jian J Wang <jian.j.wang@intel.com>, Hao A Wu <hao.a.wu@intel.com>
Subject: Re: [edk2-devel] [Patch v2] MdeModulePkg: Initialize local variable value before they are used
Date: Thu, 18 Mar 2021 15:38:51 +0100 [thread overview]
Message-ID: <5bbd0b1f-7a53-d63c-58ed-b637c47aad11@redhat.com> (raw)
In-Reply-To: <20210318045046.1909-1-gaoliming@byosoft.com.cn>
On 03/18/21 05:50, gaoliming wrote:
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=3228
> This change is to fix the false compiler error on GCC49 release build.
>
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Hao A Wu <hao.a.wu@intel.com>
> Signed-off-by: Liming Gao <gaoliming@byosoft.com.cn>
> Reviewed-by: Hao A Wu <hao.a.wu@intel.com>
> ---
> In V2, add the comments for the false compiler warning
>
> MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c | 5 +++++
> .../VariablePolicyHelperLib/VariablePolicyHelperLib.c | 5 +++++
> 2 files changed, 10 insertions(+)
>
> diff --git a/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c b/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c
> index e99a812a44..1053695b3b 100644
> --- a/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c
> +++ b/MdeModulePkg/Bus/Ata/AtaAtapiPassThru/AhciMode.c
> @@ -1127,6 +1127,11 @@ AhciDmaTransfer (
> return EFI_INVALID_PARAMETER;
> }
>
> + //
> + // Set Status to suppress incorrect compiler/analyzer warnings
> + //
> + Status = EFI_SUCCESS;
> +
> //
> // DMA buffer allocation. Needs to be done only once for both sync and async
> // DMA transfers irrespective of number of retries.
Yes, it's indeed a compiler problem. In the middle of the function, we
have control flow like this:
if (Task == NULL) {
for (Retry = 0; Retry < AHCI_COMMAND_RETRIES; Retry++) {
Status = AhciStartCommand (...);
}
} else {
if (!Task->IsStart) {
Status = AhciStartCommand (...);
}
if (Task->IsStart) {
Status = AhciCheckFisReceived (...);
}
}
There is no path through this without setting "Status", so the
subsequent warning is indeed unjustified.
> diff --git a/MdeModulePkg/Library/VariablePolicyHelperLib/VariablePolicyHelperLib.c b/MdeModulePkg/Library/VariablePolicyHelperLib/VariablePolicyHelperLib.c
> index 0c9299c8b0..6bcb95247f 100644
> --- a/MdeModulePkg/Library/VariablePolicyHelperLib/VariablePolicyHelperLib.c
> +++ b/MdeModulePkg/Library/VariablePolicyHelperLib/VariablePolicyHelperLib.c
> @@ -115,6 +115,11 @@ CreateBasicVariablePolicy (
> return EFI_INVALID_PARAMETER;
> }
>
> + //
> + // Set NameSize to suppress incorrect compiler/analyzer warnings
> + //
> + NameSize = 0;
> +
> // Now we've gotta determine the total size of the buffer required for
> // the VariablePolicy structure.
> TotalSize = sizeof( VARIABLE_POLICY_ENTRY );
>
Also correct: NameSize is only read if (Name != NULL), but in that case,
NameSize is also set. And Name does not change between the two checks.
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Thanks
Laszlo
prev parent reply other threads:[~2021-03-18 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 4:50 [Patch v2] MdeModulePkg: Initialize local variable value before they are used gaoliming
2021-03-18 14:38 ` Laszlo Ersek [this message]
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=5bbd0b1f-7a53-d63c-58ed-b637c47aad11@redhat.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