[edk2-devel] ArmPkg,ArmPlatformPkg: Adding nasm files to allow builds with VS2022

[edk2-devel] ArmPkg,ArmPlatformPkg: Adding nasm files to allow builds with VS2022

[Rebecca Cran]

I've been wondering if it might be worth adding nasm files to ArmPkg, 
ArmPlatformPkg etc. to allow platforms to be built with VS2022 - mainly 
because different compilers can detect different issues with the code.

What do people think: would it be worthwhile, or should we stick with 
GCC and CLANG and avoid the maintenance overhead of another set of 
assembly files?


-- 
Rebecca



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120675): https://edk2.groups.io/g/devel/message/120675
Mute This Topic: https://groups.io/mt/109181847/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [edk2-devel] ArmPkg,ArmPlatformPkg: Adding nasm files to allow builds with VS2022

[Sami Mujawar]

[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]

Hi Rebecca,

Thank you for bringing up this topic.

I agree we should get Visual Studio compiler support for Arm in edk2. The Visual Studio static analysis has helped to detect issues in DynamicTablesPkg in the past (when we did not have any dependency on assembly code).

I can see that Visual Studio Compiler support is already available in Project Mu. Would it be good to pull in the changes from there?
We would need to:

  *   look at the compatibility of the licenses.
  *   review and align any changes with the latest edk2 code base (Note this effort would be significantly less than starting from scratch).

@Oliver Smith-Denny<mailto:osde@linux.microsoft.com> is this something you can help with, please?

Regards,

Sami Mujawar


From: Rebecca Cran <rebecca@bsdio.com>
Date: Thursday, 24 October 2024 at 00:49
To: devel@edk2.groups.io <devel@edk2.groups.io>, Leif Lindholm <quic_llindhol@quicinc.com>, Sami Mujawar <Sami.Mujawar@arm.com>
Subject: ArmPkg,ArmPlatformPkg: Adding nasm files to allow builds with VS2022
I've been wondering if it might be worth adding nasm files to ArmPkg,
ArmPlatformPkg etc. to allow platforms to be built with VS2022 - mainly
because different compilers can detect different issues with the code.

What do people think: would it be worthwhile, or should we stick with
GCC and CLANG and avoid the maintenance overhead of another set of
assembly files?


--
Rebecca
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120680): https://edk2.groups.io/g/devel/message/120680
Mute This Topic: https://groups.io/mt/109181847/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 10710 bytes --]

Re: [edk2-devel] ArmPkg,ArmPlatformPkg: Adding nasm files to allow builds with VS2022

[Oliver Smith-Denny]

On 10/24/2024 2:08 AM, Sami Mujawar wrote:
> Hi Rebecca,
> 
> Thank you for bringing up this topic.
> 
> I agree we should get Visual Studio compiler support for Arm in edk2. 
> The Visual Studio static analysis has helped to detect issues in 
> DynamicTablesPkg in the past (when we did not have any dependency on 
> assembly code).
> 
> I can see that Visual Studio Compiler support is already available in 
> Project Mu. Would it be good to pull in the changes from there?
> 
> We would need to:
> 
>   * look at the compatibility of the licenses.
>   * review and align any changes with the latest edk2 code base (Note
>     this effort would be significantly less than starting from scratch).
> 
> @Oliver Smith-Denny <mailto:osde@linux.microsoft.com> is this something 
> you can help with, please?
> 

Yes, we have been wanting to upstream our ARM VS2022 build support,
including the nasm files, but we also weren't sure what the upstream
appetite was. I will help coordinate that from our side.

License-wise, we use the same BSD-2-Clause-Patent license as edk2
so there should be no issue.

I'll deal with any changes with the latest edk2 codebase, we are
updated to the edk2-stable202405 tag, so the delta shouldn't
be huge.

Thanks,
Oliver


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120681): https://edk2.groups.io/g/devel/message/120681
Mute This Topic: https://groups.io/mt/109181847/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [edk2-devel] ArmPkg,ArmPlatformPkg: Adding nasm files to allow builds with VS2022

[Rebecca Cran]

Awesome, thanks!

On Thu, Oct 24, 2024, at 9:48 AM, Oliver Smith-Denny wrote:
> On 10/24/2024 2:08 AM, Sami Mujawar wrote:
>> Hi Rebecca,
>> 
>> Thank you for bringing up this topic.
>> 
>> I agree we should get Visual Studio compiler support for Arm in edk2. 
>> The Visual Studio static analysis has helped to detect issues in 
>> DynamicTablesPkg in the past (when we did not have any dependency on 
>> assembly code).
>> 
>> I can see that Visual Studio Compiler support is already available in 
>> Project Mu. Would it be good to pull in the changes from there?
>> 
>> We would need to:
>> 
>>   * look at the compatibility of the licenses.
>>   * review and align any changes with the latest edk2 code base (Note
>>     this effort would be significantly less than starting from scratch).
>> 
>> @Oliver Smith-Denny <mailto:osde@linux.microsoft.com> is this something 
>> you can help with, please?
>> 
>
> Yes, we have been wanting to upstream our ARM VS2022 build support,
> including the nasm files, but we also weren't sure what the upstream
> appetite was. I will help coordinate that from our side.
>
> License-wise, we use the same BSD-2-Clause-Patent license as edk2
> so there should be no issue.
>
> I'll deal with any changes with the latest edk2 codebase, we are
> updated to the edk2-stable202405 tag, so the delta shouldn't
> be huge.
>
> Thanks,
> Oliver
>
>
> 


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120682): https://edk2.groups.io/g/devel/message/120682
Mute This Topic: https://groups.io/mt/109181847/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-