Differences

This shows you the differences between two versions of the page.

--- en:multiasm:papc:chapter_6_8 [2026/02/27 01:48] – [Callig Windows system functions] jtokarz
+++ en:multiasm:papc:chapter_6_8 [2026/05/12 15:24] (current) – [Procedures, Functions and Calls in Windows and Linux] ktokarz
@@ Line 46: / Line 46: @@
 </code>
-The Microsoft Windows x64 calling convention requires that even when the parameters are passed through registers, a 32-byte space for them should be reserved on the stack. It is referred to as a shadow space or home space. The shadow space size can be increased to store local variables of the procedure. Why does the x64 calling convention require the shadow space to be explained in the Microsoft blog article((https://devblogs.microsoft.com/oldnewthing/20160623-00/?p=93735)).\\
+The Microsoft Windows x64 calling convention requires that, even when parameters are passed in registers, a 32-byte space for them be reserved on the stack. It is referred to as a shadow space or home space. Reservation of a shadow space for arguments is the caller's responsibility. The shadow space size can be increased to store local variables of the procedure. Why does the x64 calling convention require the shadow space to be explained in the Microsoft blog article((https://devblogs.microsoft.com/oldnewthing/20160623-00/?p=93735)).\\
 Some registers are considered non-volatile. It means that they must be saved and restored by a function that uses them. They are RBX, RBP, RDI, RSI, RSP, R12, R13, R14, R15, and XMM6-XMM15.\\

en/multiasm/papc/chapter_6_8.txt · Last modified: 2026/05/12 15:24 by ktokarz