From: "Ni, Ray" <ray.ni@intel.com>
To: Andrew Fish <afish@apple.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>
Subject: Is Xcode5ExceptionHandlerAsm.nasm still needed?
Date: Thu, 30 Mar 2023 10:16:27 +0000 [thread overview]
Message-ID: <MN6PR11MB8244E7D0589C5CE6B1E171758C8E9@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
Andrew,
In UefiCpuPkg\Library\CpuExceptionHandlerLib\X64\, there are two nasm files: ExceptionHandlerAsm.nasm and the other XCODE version.
The major diff between the two is the second operand in "mov rax, ASM_PFX(CommonInterruptEntry)" is patched at runtime by code, instead of relying on linker/loader to fix it.
Can I know more background why it's needed for XCODE?
Given Apple is switching away from X86 CPU, is the XCODE version still needed?
+ Mike because I found another commit by you for bug: 565 - Fix X64 XCODE5/NASM compatibility issue in UefiCpuPkg MpInitLib (tianocore.org)<https://bugzilla.tianocore.org/show_bug.cgi?id=565>.
Thanks,
Ray
[-- Attachment #2: Type: text/html, Size: 4225 bytes --]
next reply other threads:[~2023-03-30 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:16 Ni, Ray [this message]
2023-03-30 10:48 ` [edk2-devel] Is Xcode5ExceptionHandlerAsm.nasm still needed? Ard Biesheuvel
2023-03-30 11:47 ` Ard Biesheuvel
2023-03-30 14:25 ` Ni, Ray
2023-03-30 15:04 ` Ard Biesheuvel
2023-03-30 16:33 ` Ard Biesheuvel
2023-03-30 16:47 ` Ard Biesheuvel
2023-03-30 16:54 ` Rebecca Cran
2023-03-30 17:03 ` Ard Biesheuvel
2023-03-30 15:30 ` Michael D Kinney
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=MN6PR11MB8244E7D0589C5CE6B1E171758C8E9@MN6PR11MB8244.namprd11.prod.outlook.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