The Art of ARM Assembly, Volume 1 64-Bit ARM Machine Organization and Programming (Randall Hyde)（Z-Library）

【One-Line Pitch】 A hands-on, Gas-first guide to 64-bit ARM assembly that teaches you how the machine really works—registers, memory, procedures, SIMD, and macros—so you can write faster code and understand what compilers do. Best for programmers with some C/system background who want real ARM64 fluency, not just theory. 【Book Arc】 - **Opening (~0%–10%)**: Sets up why 64-bit ARM matters (Apple Silicon, Raspberry Pi, mobile/embedded) and introduces Gas, data representation, condition flags, floating-point formats, and Operand2/large-constant mechanics—the vocabulary you need before writing real code. - **Early (~10%–30%)**: Covers memory organization and access (sections, endianness, addressing modes, push/pop), then constants, pointers, and composite types (strings, arrays, structs, unions), moving into procedures, activation records, and the ARM ABI parameter-passing conventions. - **Middle (~30%–55%)**: Low-level control structures (branches, if/switch, loops and loop optimization), advanced arithmetic and extended-precision operations, numeric conversion, and table lookups—the core of translating high-level logic into instruction sequences. - **Late (~55%–80%)**: Advanced machine-level topics: Neon/SIMD vector programming (data movement, shifts, arithmetic), bit manipulation, and the Gas compile-time language including macros and the C/C++ preprocessor. - **Ending (~80%–100%)**: Practical project work—string operations and Unicode handling, managing multi-file projects with includes, separate compilation, makefiles and archiver libraries, plus stand-alone programs using system calls; reference appendices cover ASCII, Gas installation, Bash, and C functions. 【Key Takeaways】 - **Assembly is a machine-organization teacher first, an optimization tool second** (Middle): Hyde frames the main value as understanding how hardware executes code, which improves your high-level language decisions and debugging. (Middle) - **Gas is the concrete tool throughout** (Opening): Directives, sections, alignment, and the compile-time language are treated as first-class skills, not incidental syntax. (Opening) - **Memory and addressing modes are foundational** (Early): PC-relative, register-indirect, pre/post-indexed, and scaled-indexed modes, plus stack push/pop, underpin everything that follows. (Early) - **Procedures follow a disciplined ABI** (Early): Activation records, standard entry/exit sequences, and parameter passing by value vs. reference are presented as reusable patterns. (Early) - **Control flow can be optimized systematically** (Middle): Loop improvements like moving termination conditions, backward loops, eliminating invariants, unrolling, and induction variables are concrete techniques. (Middle) - **SIMD/Neon unlocks real performance** (Late): Vector registers, vertical/horizontal operations, and saturating/narrowing shifts show how to process data in parallel. (Late) - **Macros and the compile-time language reduce repetition** (Late): Gas macros, CPP macros, conditional assembly, and compile-time loops let you generate code rather than hand-write it. (Late) - **Real projects need build infrastructure** (Ending): Separate compilation, makefiles, archiver libraries, and system-call-based stand-alone programs bridge exercises to working software. (Ending) 【Reading Tips】 - Deep-read the memory/addressing and procedure chapters early; they recur constantly and are the hardest to fake later. - Skim the reference appendices (ASCII, Bash, C functions) on first pass, then return when a build or system-call example needs them. - Treat the SIMD/Neon and macro chapters as the payoff—read them with an assembler open, since the instruction variety is dense. - Use the numeric-conversion and table-lookup chapters as worked examples of turning algorithms into instruction sequences, not as trivia. - Keep the ABI/entry-exit patterns handy as templates; most later code reuses them. 【Coverage Limits】 This guide is based on stratified excerpts (front matter, table of contents, and introduction-heavy material); later chapters are mapped from their headings rather than full prose, so specific code examples and detailed explanations are not summarized here.