After further evaluation on use of NASM with macho
there are a couple issues that need to be resolved
before the .asm and .S files can be removed from
The details are at:
NASM issues to be resolved are:
The recommendation is to not switch to NASM only
for libraries until the dead code stripping feature
works as expected on macho.
We can consider moving to NASM only for NASM files
in a module if there are no NASM functions that would
be dead stripped. The recommendation for these types
of NASM files is do not use the following pragma
until the NASM issues above are resolved.
%pragma macho subsections_via_symbols
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-
> boun...@lists.01.org] On Behalf Of Gao, Liming
> Sent: Wednesday, January 31, 2018 3:06 AM
> To: firstname.lastname@example.org
> Subject: [edk2] [RFC] Remove X86 .asm and .S assembly
> files in EDK2
> Edk2 has used nasm assembly file for all tool chains.
> So, IA32 and X64 .asm and .S assembly files can be
> removed if their nasm files are ready. It can save the
> maintain effort and avoid the confuse.
> If you have any comments on this change, please let me
> edk2-devel mailing list
edk2-devel mailing list