From: "Laszlo Ersek" <lersek@redhat.com>
To: Leif Lindholm <leif@nuviainc.com>, devel@edk2.groups.io
Cc: Pierre Gondois <pierre.gondois@arm.com>, Bob Feng <bob.c.feng@intel.com>
Subject: Re: [PATCH 1/1] EmbeddedPkg: fix gcc build errors in AndroidBootImgLib
Date: Wed, 22 Jul 2020 22:34:52 +0200 [thread overview]
Message-ID: <4f591b72-94de-8a67-76dc-f82c41e11523@redhat.com> (raw)
In-Reply-To: <20200721125056.32195-1-leif@nuviainc.com>
On 07/21/20 14:50, Leif Lindholm wrote:
> Commit dbd546a32d5a
> ("BaseTools: Add gcc flag to warn on void* pointer arithmetic")
> does its work and triggers build errors in this library.
> Update the affected code to build correctly again.
>
> Cc: Pierre Gondois <pierre.gondois@arm.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Bob Feng<bob.c.feng@intel.com>
> Signed-off-by: Leif Lindholm <leif@nuviainc.com>
> ---
>
> Pierre - can you please ensure to CC Arm maintainers when proposing
> changes to Arm build flags? (And build test all the top-level edk2
> packages *cough*.)
or we could perhaps introduce
EmbeddedPkg/EmbeddedPkg.ci.yaml
>
> Bob - can you please ensure Arm maintainers have commented on changes to
> global build flags?
> (Would it be possible to break up tools_def.template into separate
> arch-specific include files so we could have GetMaintainer.py be
> more helpful for this?)
>
> Laszlo - you're not formally an EmbeddedPkg reviewer, but Ard is out for
> another couple of weeks. But since the Linaro CI is currently broken and
> the fix is trivial, could you have a look please?
>
> EmbeddedPkg/Library/AndroidBootImgLib/AndroidBootImgLib.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/EmbeddedPkg/Library/AndroidBootImgLib/AndroidBootImgLib.c b/EmbeddedPkg/Library/AndroidBootImgLib/AndroidBootImgLib.c
> index e1036954ee58..15b5bf451330 100644
> --- a/EmbeddedPkg/Library/AndroidBootImgLib/AndroidBootImgLib.c
> +++ b/EmbeddedPkg/Library/AndroidBootImgLib/AndroidBootImgLib.c
> @@ -97,7 +97,7 @@ AndroidBootImgGetKernelInfo (
> ASSERT (IS_VALID_ANDROID_PAGE_SIZE (Header->PageSize));
>
> *KernelSize = Header->KernelSize;
> - *Kernel = BootImg + Header->PageSize;
> + *Kernel = (VOID *)((UINTN)BootImg + Header->PageSize);
> return EFI_SUCCESS;
> }
>
Header->PageSize has type UINT32, so this is OK (the addition is
performed in UINTN, so the conversion back to VOID* is from UINTN).
> @@ -341,7 +341,7 @@ AndroidBootImgUpdateFdt (
>
> Status = AndroidBootImgSetProperty64 (UpdatedFdtBase, ChosenNode,
> "linux,initrd-end",
> - (UINTN)(RamdiskData + RamdiskSize));
> + ((UINTN)RamdiskData + RamdiskSize));
> if (EFI_ERROR (Status)) {
> goto Fdt_Exit;
> }
>
RamdiskSize is a UINTN, so this is OK too.
(You could even strip the outer parentheses:
(UINTN)RamdiskData + RamdiskSize
)
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Thanks
Laszlo
next prev parent reply other threads:[~2020-07-22 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 12:50 [PATCH 1/1] EmbeddedPkg: fix gcc build errors in AndroidBootImgLib Leif Lindholm
2020-07-21 13:18 ` PierreGondois
2020-07-22 15:24 ` Leif Lindholm
2020-07-21 14:26 ` Bob Feng
2020-07-22 20:34 ` Laszlo Ersek [this message]
2020-07-23 10:57 ` Leif Lindholm
2020-07-23 12:08 ` Leif Lindholm
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=4f591b72-94de-8a67-76dc-f82c41e11523@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