public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@nuviainc.com>
To: devel@edk2.groups.io, lersek@redhat.com, rebecca@bsdio.com
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
	Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] Build fails with VS2012
Date: Mon, 10 May 2021 07:20:48 -0600	[thread overview]
Message-ID: <a6b8e94d-c886-bac9-be02-4a53c291f5c7@nuviainc.com> (raw)
In-Reply-To: <0ef244cf-7100-4f1b-29f5-607e9e243061@redhat.com>

On 5/10/21 5:56 AM, Laszlo Ersek wrote:
> Hi Rebecca
> 
> +Tom
> 
> On 05/08/21 21:47, Rebecca Cran wrote:
>> I'm setting up a new Jenkins server to do Bhyve builds and run on
>> platforms that aren't currently tested with the GitHub/Azure system.
>>
>> Since VS2012 appears to be a supported toolchain, I tried building
>> OvmfPkgX64 with it (I'm also planning on testing VS2013, VS2015, VS2017
>> and VS2019), but it fails with:
>>
>>
>> Building ...
>> c:\users\administrator\src\edk2\NetworkPkg\Library\DxeUdpIoLib\DxeUdpIoLib.inf
>> [X64]
>> c:\users\administrator\src\edk2\UefiCpuPkg\Library\MpInitLib\MpLib.c(1268)
>> : error C2220: warning treated as error - no 'object' file generated
>> c:\users\administrator\src\edk2\UefiCpuPkg\Library\MpInitLib\MpLib.c(1268)
>> : warning C4306: 'type cast' : conversion from 'int' to
>> 'SEV_ES_AP_JMP_FAR *' of greater size
> 
> I think the compiler is justified to complain here:
> 
> 7b7508ad784d1 (Tom Lendacky     2020-08-12 15:21:42 -0500 1268)   JmpFar = (SEV_ES_AP_JMP_FAR *) FixedPcdGet32 (PcdSevEsWorkAreaBase);
> 
> The proper way to spell such casts is with (UINTN) in the middle.
> 
> Can you please file a new BZ?

I've created https://bugzilla.tianocore.org/show_bug.cgi?id=3385

>> I know the GitHub/Azure system only tests with VS2017 and VS2019: are
>> there plans to drop the older VS versions, or should they still work?
>> And would it be considered useful to _check_ that they still work, or
>> should they be considered unsupported?
> 
> I'd suggest dropping them.
> 
> Earlier, Ard raised a similar question for gcc too -- IIRC, Ard suggested that GCC4* be removed. I agree with the idea.

Thanks. If we're ready to go ahead, should I create a patch to remove them?

Do you know what the new minimum version of gcc should then be? I'd like 
to run builds with it so we can catch any issues.

Would we remove all VS versions except VS2017 and VS2019, or would we 
keep others like VS2015 for now?

-- 
Rebecca Cran

  reply	other threads:[~2021-05-10 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08 19:47 Build fails with VS2012 Rebecca Cran
2021-05-10 11:56 ` [edk2-devel] " Laszlo Ersek
2021-05-10 13:20   ` Rebecca Cran [this message]
2021-05-10 23:31     ` Michael D Kinney
2021-05-11  0:14       ` Rebecca Cran
2021-05-11 14:41         ` Laszlo Ersek
2021-05-12  0:04           ` Andrew Fish
     [not found] <167D2F1936103629.17661@groups.io>
2021-05-09 17:42 ` Rebecca Cran
2021-05-10 11:59   ` 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=a6b8e94d-c886-bac9-be02-4a53c291f5c7@nuviainc.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