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
Copy file name to clipboardExpand all lines: docs/build/reference/hotpatch-create-hotpatchable-image.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Prepares an image for hot patching.
23
23
24
24
When `/hotpatch` is used in compilation, the compiler ensures that the first instruction of each function is at least 2 bytes long, and no jump within the function goes to the first instruction. These conditions are required for hot patching.
25
25
26
-
To complete the preparation for making an image hotpatchable, after you use `/hotpatch` to compile, you must use [`functionpadmin`](functionpadmin-create-hotpatchable-image.md) (Create Hotpatchable Image)]to link. When you compile and link an image by using one invocation of cl.exe, `/hotpatch` implies `/functionpadmin`.
26
+
To complete the preparation for making an image hotpatchable, after you use `/hotpatch` to compile, you must use [`/functionpadmin`](functionpadmin-create-hotpatchable-image.md) (Create Hotpatchable Image)]to link. When you compile and link an image by using one invocation of cl.exe, `/hotpatch` implies `/functionpadmin`.
27
27
28
28
> [!TIP]
29
29
> Arm64 and x64 architectures are always treated as hotpatchable. But you must still link by using `/functionpadmin` to create hotpatchable images for them.
0 commit comments