從畫面上可以看到我的顯示晶片是Quadro NVS 140M，然後你可以點選【測試DirectDraw】
而知道的問題的原因之後，就開始針對Quadro NVS 140M來找解決方案!| xxxxxxx0 | .. rest of stack .. | |
| xxxxxxx8 | return address | <- RSP |
Due to the presence of the return address, the stack is misaligned. CallThatFunction sets up its stack frame, which might go like this:
sub rsp, 0x28
Notice that the local stack frame size is 16n+8, so that the result is a realigned stack.
| xxxxxxx0 | .. rest of stack .. | |
| xxxxxxx8 | return address | |
| xxxxxxx0 | (arg5) | |
| xxxxxxx8 | (arg4 spill) | |
| xxxxxxx0 | (arg3 spill) | |
| xxxxxxx8 | (arg2 spill) | |
| xxxxxxx0 | (arg1 spill) <- RSP |
Now we can set up for the first call:
mov dword ptr [rsp+0x20], 5 ; output parameter 5
mov r9d, 4 ; output parameter 4
mov r8d, 3 ; output parameter 3
mov rdx, 2 ; output parameter 2
mov rcx, 1 ; output parameter 1
call SomeFunction ; Go Speed Racer!
When SomeFunction returns, the stack is not cleaned, so it still looks like it did above. To issue the second call, then, we just shove the new values into the space we already reserved:
mov dword ptr [rsp+0x20], 10 ; output parameter 5CallThatFunction is now finished and can clean its stack and return.
mov r9d, 9 ; output parameter 4
mov r8d, 8 ; output parameter 3
mov rdx, 7 ; output parameter 2
mov rcx, 6 ; output parameter 1
call SomeFunction ; Go Speed Racer!
add rsp, 0x28
ret
Notice that you see very few "push" instructions in amd64 code, since the paradigm is for the caller to reserve parameter space and keep re-using it.
這種呼叫慣例比較像是結合了__cdecl/ __fastcall 的特性:
