Logo Questions Linux Laravel Mysql Ubuntu Git Menu
HTML CSS JAVASCRIPT SQL PYTHON PHP BOOTSTRAP JAVA JQUERY R React Kotlin
 

New posts in calling-convention

Is the stack aligned to a 4 bytes boundary when my program starts?

assembly x86 stack memory-alignment calling-convention

Is Tail Call Optimization intentionally not used for `vector<T> foo() { return bar(); }`, given `vector<T> bar();`? [duplicate]

c gcc optimization x86-64 calling-convention

Why does a mismatching printf specifier also affect subsequent arguments?

c printf undefined-behavior variadic-functions calling-convention

Calling Rust functions from inline assembly and calling conventions

c rust calling-convention

Calling C function from x64 assembly with registers instead of stack

assembly x86-64 calling-convention gnu-assembler

How are parameters passed to Linux system call ? Via register or stack?

c linux linux-kernel system-calls calling-convention

Can stdcall have a variable arguments?

windows winapi calling-convention stdcall variadic-functions

std::sort & comp - calling convention?

c++ sorting calling-convention

R7 and R11 relation with Link Register in ARM architecture (thumb/arm) calling convention

arm calling-convention thumb

Why is GCC with __attribute__((__ms_abi__)) returning values differently than MSVC does?

c gcc x86 calling-convention abi

Where is the offset of the Y register from the call/stack frame in avr-gcc coming from?

assembly avr calling-convention avr-gcc frame-pointer

Why Assembly x86_64 syscall parameters are not in alphabetical order like i386

assembly x86 x86-64 cpu-registers calling-convention

Does the ARM calling convention allow a function to not store LR to the stack?

assembly arm standards calling-convention

NASM should I pop function argument after calling a function?

assembly x86-64 nasm callstack calling-convention

What is the "sub $16, %rsp" instruction being used for?

assembly gcc x86-64 calling-convention

Why can't we move directly 1 byte from stack's frame to register?

gcc assembly x86-64 calling-convention function-parameter

How can one protect a register from being overwritten during a function call?

c++ c assembly calling-convention
Older Entries »