You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tracking issue for the "efiapi" calling convention #65815
Tracking issue for the efiapi calling convention, added in PR #65809. The feature gate name is abi_efiapi.
The efiapi calling convention can be used for defining a function with an ABI compatible with the UEFI Interfaces as defined in the UEFI Specification. On the currently supported platform, this means selecting between the win64 ABI or the C ABI depending on the target architecture.
Usage
extern"efiapi"fnfunc(){…}
Known Issues
The ABI is currently accessible on platforms architectures not supported by UEFI (x86, x86_64, itanium, arm, arm64 and risc-v). There is currently no way to whitelist ABI for certain architectures, see AAPCS ABI is accepted for x86 target #57182 for a similar issue.
EFIAPI should delegate to aapcs on ARM, and aapcs64 en ARM64, instead of delegating to C.
Tracking issue for the
efiapicalling convention, added in PR #65809. The feature gate name isabi_efiapi.The
efiapicalling convention can be used for defining a function with an ABI compatible with the UEFI Interfaces as defined in the UEFI Specification. On the currently supported platform, this means selecting between thewin64ABI or theCABI depending on the target architecture.Usage
Known Issues
aapcson ARM, andaapcs64en ARM64, instead of delegating toC.