/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

samwho.dev
| | shellsharks.com

An introduction to x86 Intel assembly.
3.2 parsecs

Travel
| |
| | mcyoung.xyz

[AI summary] The article provides an in-depth exploration of computer architecture and assembly language, focusing on the RISC-V Instruction Set Architecture (ISA). It covers fundamental concepts such as machine words, registers, and the role of assembly language as a human-readable representation of machine instructions. The text explains how programs are structured using instructions, labels, and directives, and categorizes instructions into arithmetic, memory, control flow, and miscellaneous types. It also delves into the calling convention, which defines how functions are called and how data is passed between them, and highlights the importance of maintaining the call stack illusion. The article further discusses the practical implications of these conce...
2.8 parsecs

Travel
| |
| | gpfault.net

[AI summary] The provided text is a detailed explanation of how to write a simple 64-bit Windows application in assembly language that calls the ExitProcess function from the KERNEL32.DLL library. It covers the following key topics: 1. **Memory and Register Basics**: Explains how memory and registers work in 64-bit Windows, including the use of the stack pointer (RSP), registers like RCX, RDX, R8, and R9 for passing arguments, and the importance of stack alignment for performance. 2. **Calling Conventions**: Details the 64-bit Windows calling convention, including how the first four integer or pointer arguments are passed in registers (RCX, RDX, R8, R9), how additional arguments are passed on the stack, and the requirement for the stack to be aligned to ...
2.9 parsecs

Travel
| |
| | binarydebt.wordpress.com

System call table is an array of function pointers. It is defined in kernel space as variable sys_call_table and it contains pointers to functions which implement system calls. Index of each function pointer in the array is the system call number for that syscall. These are denoted by NR_* macros in header files, such as...
24.8 parsecs

Travel
|