Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
mohitmishra786 avatar

Assembly X86

  • 383 installs
  • 155 repo stars
  • Updated June 27, 2026
  • mohitmishra786/low-level-dev-skills

assembly-x86 is a Claude Code agent skill that teaches x86-64 assembly reading, writing, and debugging with System V AMD64 ABI conventions for developers optimizing performance-critical C, C++, or Rust routines.

About

assembly-x86 is a low-level-dev-skills agent skill for x86-64 assembly from the mohitmishra786 toolchain suite. The skill documents System V AMD64 ABI register roles across rdi, rsi, rdx, rcx, r8, r9 argument slots, xmm0–xmm7 SIMD args, callee-saved rbx/rbp/r12–r15, and the 128-byte red zone. Developers reach for assembly-x86 when reading GCC -S output in AT&T or Intel syntax, writing inline asm in C/C++, debugging rsp/rbp stack frames in GDB, or applying SSE, AVX, and AVX-512 intrinsics in hot paths.

  • Covers x86 instruction patterns and register usage
  • Explains ABI, stacks, and calling conventions
  • Supports debugging and optimizing tight native loops
  • Bridges high-level code with machine-level behavior

Assembly X86 by the numbers

  • 383 all-time installs (skills.sh)
  • +26 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #115 of 782 Skill Development skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mohitmishra786/low-level-dev-skills --skill assembly-x86

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs383
repo stars155
Last updatedJune 27, 2026
Repositorymohitmishra786/low-level-dev-skills

How do you read x86-64 GCC assembly output?

Write, read, and debug x86 assembly for performance-critical routines, ABI-compliant calls, and low-level systems work when higher-level languages are insufficient.

Who is it for?

Systems programmers debugging x86-64 disassembly, writing inline asm in C/C++/Rust, or optimizing hot paths with SIMD intrinsics on Linux or macOS.

Skip if: Developers building standard web frontends or managed-language services without compiler assembly output or register-level debugging needs.

When should I use this skill?

A user asks about x86-64 registers, System V AMD64 calling convention, AT&T vs Intel syntax, or reading disassembly from objdump or GDB.

What you get

Correct x86-64 assembly with System V AMD64 ABI register usage, inline asm constraints, and annotated objdump or GDB disassembly.

  • ABI-compliant inline asm blocks
  • Annotated AT&T or Intel disassembly

By the numbers

  • Documents 6 integer argument registers plus r8 and r9 on System V AMD64
  • Covers 128-byte red zone below rsp for leaf function optimization

Files

SKILL.mdMarkdownGitHub ↗

x86-64 Assembly

Purpose

Guide agents through x86-64 assembly: reading compiler output, understanding the ABI, writing inline asm, and common patterns.

Triggers

  • "How do I read the assembly GCC generated?"
  • "What are the x86-64 registers?"
  • "What is the calling convention on Linux/macOS?"
  • "How do I write inline assembly in C?"
  • "How do I use SSE/AVX intrinsics?"
  • "This assembly uses %rsp / %rbp — what does it mean?"

Workflow

1. Generate and read assembly

# AT&T syntax (GCC default)
gcc -S -O2 -fverbose-asm foo.c -o foo.s

# Intel syntax
gcc -S -masm=intel -O2 foo.c -o foo.s

# From GDB
(gdb) disassemble /s main    # with source
(gdb) x/20i $rip

# From objdump
objdump -d -M intel -S prog  # Intel + source (needs -g)

2. x86-64 registers

64-bit32-bit16-bit8-bit high8-bit lowPurpose
%rax%eax%ax%ah%alReturn value / accumulator
%rbx%ebx%bx%bh%blCallee-saved
%rcx%ecx%cx%ch%cl4th arg / count
%rdx%edx%dx%dh%dl3rd arg / 2nd return
%rsi%esi%si%sil2nd arg
%rdi%edi%di%dil1st arg
%rbp%ebp%bp%bplFrame pointer (callee-saved)
%rsp%esp%sp%splStack pointer
%r8%r11%r8d%r11d%r8w%r11w%r8b%r11b5th–8th args / caller-saved
%r12%r15%r12d%r15d%r12w%r15w%r12b%r15bCallee-saved
%ripInstruction pointer
%rflags%eflagsStatus flags
%xmm0%xmm7FP/SIMD args and return
%xmm8%xmm15Caller-saved SIMD
%ymm0%ymm15AVX 256-bit
%zmm0%zmm31AVX-512 512-bit

3. System V AMD64 ABI (Linux, macOS, FreeBSD)

Integer/pointer argument registers (in order): %rdi, %rsi, %rdx, %rcx, %r8, %r9

Floating-point argument registers: %xmm0%xmm7

Return values:

  • Integer: %rax (low), %rdx (high if 128-bit)
  • Float: %xmm0 (low), %xmm1 (high)

Caller-saved (scratch): %rax, %rcx, %rdx, %rsi, %rdi, %r8–%r11, %xmm0–%xmm15

Callee-saved (must preserve): %rbx, %rbp, %r12–%r15

Stack: 16-byte aligned before call; call pushes 8 bytes → 16-byte aligned at function entry after prologue.

Red zone: 128 bytes below %rsp may be used by leaf functions without adjusting %rsp. Not available in kernel/signal handlers.

4. Common instruction patterns

PatternMeaning
mov %rdi, %raxCopy rdi to rax
mov (%rdi), %raxLoad 8 bytes from address in rdi
mov %rax, 8(%rdi)Store rax to rdi+8
lea 8(%rdi), %raxLoad effective address rdi+8 into rax (no memory access)
push %rbxPush rbx; rsp -= 8
pop %rbxPop into rbx; rsp += 8
call fooPush return addr; jmp foo
retPop return addr; jmp to it
xor %eax, %eaxZero rax (smaller encoding than mov $0, %rax)
test %rax, %raxSet ZF if rax == 0 (cheaper than cmp $0, %rax)
cmp $5, %rdiSet flags for rdi - 5
jl labelJump if signed less than

5. AT&T vs Intel syntax

FeatureAT&TIntel
Operand ordersource, destdest, source
Register prefix%raxrax
Immediate prefix$4242
Memory operand8(%rdi)[rdi+8]
Size suffixmovl, movq— (inferred)

GCC emits AT&T by default. Use -masm=intel for Intel syntax.

6. Inline assembly (GCC extended asm)

// Basic: increment a register
int x = 5;
__asm__ volatile (
    "incl %0"
    : "=r"(x)   // outputs: =r means write-only register
    : "0"(x)    // inputs: 0 means same as output 0
    : // clobbers: none
);

// CPUID example
uint32_t eax, ebx, ecx, edx;
__asm__ volatile (
    "cpuid"
    : "=a"(eax), "=b"(ebx), "=c"(ecx), "=d"(edx)
    : "a"(1)    // input: leaf 1
);

// Atomic increment
static inline int atomic_inc(volatile int *p) {
    int ret;
    __asm__ volatile (
        "lock; xaddl %0, %1"
        : "=r"(ret), "+m"(*p)
        : "0"(1)
        : "memory"
    );
    return ret + 1;
}

Constraint codes:

  • "r" — any general register
  • "m" — memory operand
  • "i" — immediate integer
  • "a", "b", "c", "d" — specific registers (%rax, %rbx, %rcx, %rdx)
  • "=" prefix — output (write-only)
  • "+" prefix — read-write
  • "memory" clobber — tells compiler memory may be modified (barrier)

7. SSE/AVX intrinsics (preferred over inline asm)

#include <immintrin.h>   // includes all x86 SIMD headers

// Add 8 floats at once with AVX
__m256 a = _mm256_loadu_ps(arr_a);   // load 8 floats (unaligned)
__m256 b = _mm256_loadu_ps(arr_b);
__m256 c = _mm256_add_ps(a, b);
_mm256_storeu_ps(result, c);

Check CPU support at compile time: -mavx2 or -march=native. Check at runtime: __builtin_cpu_supports("avx2").

For a full register and instruction reference, see references/reference.md.

Related skills

  • Use skills/low-level-programming/assembly-arm for AArch64/ARM assembly
  • Use skills/compilers/gcc for -S -masm=intel flag details
  • Use skills/debuggers/gdb for stepping through assembly (si, ni, x/i)

Related skills

How it compares

Pick assembly-x86 over assembly-arm when debugging Linux or macOS x86-64 compiler output, SIMD intrinsics, or System V AMD64 ABI compliance.

FAQ

What calling convention does assembly-x86 document?

assembly-x86 documents the System V AMD64 ABI used on Linux, macOS, and FreeBSD. Integer arguments pass through rdi, rsi, rdx, rcx, r8, and r9, with floating-point args in xmm0–xmm7 and returns in rax or xmm0.

How does assembly-x86 switch between AT&T and Intel syntax?

assembly-x86 generates AT&T syntax with gcc -S -O2 by default and Intel syntax with gcc -S -masm=intel -O2. Disassembly uses objdump -d -M intel -S for Intel syntax with source interleaving.

Skill Developmentbackendtesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.