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
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.