More Related Contents:
- Why does Windows64 use a different calling convention from all other OSes on x86-64?
- What are the calling conventions for UNIX & Linux system calls (and user-space functions) on i386 and x86-64
- Where is the x86-64 System V ABI documented?
- What registers are preserved through a linux x86-64 function call
- Where exactly is the red zone on x86-64?
- Is it valid to write below ESP?
- C++ on x86-64: when are structs/classes passed and returned in registers?
- What’s the best way to remember the x86-64 System V arg register order?
- Shadow space example
- What happens if you use the 32-bit int 0x80 Linux ABI in 64-bit code?
- What are callee and caller saved registers?
- Why does the x86-64 / AMD64 System V ABI mandate a 16 byte stack alignment?
- glibc scanf Segmentation faults when called from a function that doesn’t align RSP
- Is a sign or zero extension required when adding a 32bit offset to a pointer for the x86-64 ABI?
- Why does this function push RAX to the stack as the first operation?
- How to print a single-precision float with printf
- Windows system calls [duplicate]
- Compiling assembly in Visual Studio
- System Calls in windows & Native API?
- 64-bit syscall documentation for MacOS assembly
- Does each PUSH instruction push a multiple of 8 bytes on x64?
- Hello world using nasm in windows assembly
- Why can a T* be passed in register, but a unique_ptr cannot?
- Why is RCX not used for passing parameters to system calls, being replaced with R10? [duplicate]
- Segmentation fault on printf – NASM 64bit Linux
- Why does the x86-64 System V calling convention pass args in registers instead of just the stack?
- How do vararg functions find out the number of arguments in machine code?
- What kind of C11 data type is an array according to the AMD64 ABI
- Is reserving stack space necessary for functions less than four arguments?
- Linux x64: why does r10 come before r8 and r9 in syscalls?