This doesn't seem to mention the overhead that ARM64EC imposes on indirect calls. Indirect calls are required by the ARM64EC ABI to use a CFG-like check against

This doesn't seem to mention the overhead that ARM64EC imposes on indirect calls. Indirect calls are required by the ARM64EC ABI to use a CFG-like check against the architecture bitmap, adding overhead to both function pointers and virtual calls: https://gcc.godbolt.org/z/8aT793GMf https://gcc.godbolt.org/z/8aT793GMf This is explained in the docs: https://learn.microsoft.com/en-us/windows/arm/arm64ec-abi https://learn.microsoft.com/en-us/windows/arm/arm64ec-abi > Call checkers are optional on all other Windows ABIs, but mandatory on Arm64EC. On Arm64EC, call checkers accumulate the task of verifying the architecture of the function being called. They verify whether the call is another EC (“Emulation Compatible”) function or an x64 function that must be executed under emulation. In many cases, this can only be verified at runtime.