From: "Bi, Dandan" <dandan.bi@intel.com>
To: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Laszlo Ersek <lersek@redhat.com>, "Gao, Liming" <liming.gao@intel.com>
Subject: Re: [patch] OvmfPkg/QemuBootOrderLib: Fix NOOPT build failure
Date: Wed, 8 Feb 2017 07:15:18 +0000 [thread overview]
Message-ID: <3C0D5C461C9E904E8F62152F6274C0BB3B894002@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <148653651702.19501.2422588150276024393@jljusten-ivb>
Hi Jordan,
Yes, it fails on IA32.
As far as I know, it impacts VS2012/2013/2015.
I will create a new patch and add the impacted toolchain and arch info to the commit message.
Thanks,
Dandan
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Jordan Justen
Sent: Wednesday, February 8, 2017 2:49 PM
To: Bi, Dandan <dandan.bi@intel.com>; edk2-devel@lists.01.org
Cc: Laszlo Ersek <lersek@redhat.com>; Gao, Liming <liming.gao@intel.com>
Subject: Re: [edk2] [patch] OvmfPkg/QemuBootOrderLib: Fix NOOPT build failure
On 2017-02-07 21:55:52, Dandan Bi wrote:
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Dandan Bi <dandan.bi@intel.com>
> ---
> OvmfPkg/Library/QemuBootOrderLib/ExtraRootBusMap.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/OvmfPkg/Library/QemuBootOrderLib/ExtraRootBusMap.c
> b/OvmfPkg/Library/QemuBootOrderLib/ExtraRootBusMap.c
> index ec42214..1bb89d4 100644
> --- a/OvmfPkg/Library/QemuBootOrderLib/ExtraRootBusMap.c
> +++ b/OvmfPkg/Library/QemuBootOrderLib/ExtraRootBusMap.c
> @@ -306,8 +306,8 @@ MapRootBusPosToBusNr (
> return EFI_INVALID_PARAMETER;
> }
> if (RootBusPos > ExtraRootBusMap->Count) {
> return EFI_NOT_FOUND;
> }
> - *RootBusNr = ExtraRootBusMap->BusNumbers[RootBusPos - 1];
> + *RootBusNr = ExtraRootBusMap->BusNumbers[(UINT32)RootBusPos - 1];
Is this failing on IA32? If so, think UINTN would be better.
You might also want to add the impacted toolchain and arch to the commit message.
-Jordan
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-02-08 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 5:55 [patch] OvmfPkg/QemuBootOrderLib: Fix NOOPT build failure Dandan Bi
2017-02-08 6:48 ` Jordan Justen
2017-02-08 7:15 ` Bi, Dandan [this message]
2017-02-08 9:12 ` Laszlo Ersek
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=3C0D5C461C9E904E8F62152F6274C0BB3B894002@shsmsx102.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