public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH v2] BaseTools: align ENCODE_ERROR macro with MdePkg version
Date: Thu, 7 Dec 2017 02:41:25 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E18B9C7@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20171205161016.12879-1-leif.lindholm@linaro.org>

Leif:
  Could you also update ENCODE_WARNING() and RETURN_ERROR() to align to MdePkg?

Thanks
Liming
>-----Original Message-----
>From: Leif Lindholm [mailto:leif.lindholm@linaro.org]
>Sent: Wednesday, December 06, 2017 12:10 AM
>To: edk2-devel@lists.01.org
>Cc: Zhu, Yonghong <yonghong.zhu@intel.com>; Gao, Liming
><liming.gao@intel.com>
>Subject: [PATCH v2] BaseTools: align ENCODE_ERROR macro with MdePkg
>version
>
>BaseTools' BaseTypes.h defined the ENCODE_ERROR macro as
> #define ENCODE_ERROR(a)              ((RETURN_STATUS)(MAX_BIT | (a)))
>whereas MdePkg defines it as
> #define ENCODE_ERROR(StatusCode)     ((RETURN_STATUS)(MAX_BIT |
>(StatusCode)))
>
>When building with GCC 6.3 (at least) the former triggers
>"error: overflow in implicit constant conversion [-Werror=overflow]"
>Resolve this by aligning it with the latter one.
>
>This also requires aligning the BaseTools typedef of RETURN_STATUS with
>the MdePkg one: INTN -> UINTN.
>
>Add an explicit initialization of *Alignment to 0 in GenFfs.c
>GetAlignmentFromFile to get rid of a warning occuring with GCC after
>this change (-Werror=maybe-uninitialized).
>
>Contributed-under: TianoCore Contribution Agreement 1.1
>Signed-off-by: Leif Lindholm <leif.lindholm@linaro.org>
>---
>
>Sending out a v2 because I got cought out by the leading # in the commit
>message...
>
> BaseTools/Source/C/GenFfs/GenFfs.c            | 1 +
> BaseTools/Source/C/Include/Common/BaseTypes.h | 4 ++--
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
>diff --git a/BaseTools/Source/C/GenFfs/GenFfs.c
>b/BaseTools/Source/C/GenFfs/GenFfs.c
>index e2fb3e0d1e..3b4a9b7761 100644
>--- a/BaseTools/Source/C/GenFfs/GenFfs.c
>+++ b/BaseTools/Source/C/GenFfs/GenFfs.c
>@@ -529,6 +529,7 @@ GetAlignmentFromFile(char *InFile, UINT32
>*Alignment)
>
>   InFileHandle        = NULL;
>   PeFileBuffer        = NULL;
>+  *Alignment          = 0;
>
>   memset (&ImageContext, 0, sizeof (ImageContext));
>
>diff --git a/BaseTools/Source/C/Include/Common/BaseTypes.h
>b/BaseTools/Source/C/Include/Common/BaseTypes.h
>index 198647ab95..5fa4e560d8 100644
>--- a/BaseTools/Source/C/Include/Common/BaseTypes.h
>+++ b/BaseTools/Source/C/Include/Common/BaseTypes.h
>@@ -170,12 +170,12 @@
> // EFI Error Codes common to all execution phases
> //
>
>-typedef INTN RETURN_STATUS;
>+typedef UINTN RETURN_STATUS;
>
> ///
> /// Set the upper bit to indicate EFI Error.
> ///
>-#define ENCODE_ERROR(a)              (MAX_BIT | (a))
>+#define ENCODE_ERROR(a)              ((RETURN_STATUS)(MAX_BIT | (a)))
>
> #define ENCODE_WARNING(a)            (a)
> #define RETURN_ERROR(a)              ((a) < 0)
>--
>2.11.0



      reply	other threads:[~2017-12-07  2:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 16:10 [PATCH v2] BaseTools: align ENCODE_ERROR macro with MdePkg version Leif Lindholm
2017-12-07  2:41 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E18B9C7@SHSMSX104.ccr.corp.intel.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