Skip to content

Adding __fastfail encoding for Windows ARM64 #759

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 1, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/intrinsics/fastfail.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,7 @@ Internally, `__fastfail` is implemented by using several architecture-specific m
|x86|int 0x29|ecx|
|x64|int 0x29|rcx|
|ARM|Opcode 0xDEFB|r0|
|ARM64|Opcode 0xF003|x0|

A fast fail request is self-contained and typically requires just two instructions to execute. Once a fast fail request has been executed the kernel then takes the appropriate action. In user-mode code, there are no memory dependencies beyond the instruction pointer itself when a fast fail event is raised. This maximizes its reliability even if there is severe memory corruption.

Expand All @@ -50,12 +51,12 @@ Support for the native fast fail mechanism began in Windows 8. Windows operating

|Intrinsic|Architecture|
|---------------|------------------|
|`__fastfail`|x86, x64, ARM|
|`__fastfail`|x86, x64, ARM, ARM64|

**Header file** \<intrin.h>

**END Microsoft Specific**

## See Also

[Compiler Intrinsics](../intrinsics/compiler-intrinsics.md)
[Compiler Intrinsics](../intrinsics/compiler-intrinsics.md)