Welcome to the code repository for our book! APCASE is a very practical and comprehensive educational text for students, educators, and professionals seeking to learn about Assembly programming and computer architecture. But what makes our book helpful and unique?

• Based on a dominant architecture - x86 and x86_64 - and what you learn will be transferable to other architectures.
• All programming examples are provided for three common assemblers: GAS (Clang/LLVM), MASM, and NASM, which ensures both AT&T and Intel syntax. This allows for learning on any OS platform: Mac, Windows, and Linux.
• Context and examples provided in both 32-bit and 64-bit, both of which are useful for a programmer.
• Code-oriented and detailed overviews of function calls, floating-point operations (x87 through AVX), inline Assembly, intrinsics, and system calls, all in one book.
• Brief introduction and code examples for other modern architectures like ARM, AVR, RISC-V, and z/Architecture.
• The Appendices provide practical information and guide students in learning Assembly programming.
• Chapter Supplements provide a deeper dive on topics as necessary.
• Links to wikis, developer resources, and videos are provided to assist in further exploration of topics.
• Attention, Programming, and Learning notes are placed throughout the text to guide the reader in beneficial ways.

Is this book for you? Checkout the Preface, a free Chapter 3: Assembly and Syntax Fundamentals, and the free Appendices.

Appendices A, B, E, and I are available for free.

• Introduction to the Appendices
• Appendix A: Assembly Translation
• Appendix B: Environment Setup
• Appendix C: Disassembly
• Appendix D: Command-Line Debugging Assembly with GDB
• Appendix E: Linking Assembly and C++
• Appendix F: Functions and Stack
• Appendix G: Using CPUID
• Appendix H: ASCII and Decimal Arithmetic
• Appendix I: Intrinsics

• Prospect Press (@ProspectPressVT): https://www.prospectpressvt.com/textbooks/Hall-assembly-programming-2-0
• YouTube Channel (Book Videos): https://www.youtube.com/channel/UCr0svQEez3UQvlj6-5EYS6w
• Brian's Website: https://www.brianrhall.com
• Kevin's Website: https://www.kevinslonka.com
• Organized collection of all links in APCASE: Book_Links.md

When citing code snippets or other content from the repository or book, please cite the original source:

BibTeX:

@Book{APCASE,
author = {Hall, B. R. and Slonka, K. J.},
title = {Assembly Programming and Computer Architecture for Software Engineers},
publisher = {Prospect Press},
year = 2020,
address = {Burlington, VT},
edition = 2,
isbn = {978-1-943153-32-9}
}

@Book{APCASE,
author = {Hall, B. R. and Slonka, K. J.},
title = {Assembly Programming and Computer Architecture for Software Engineers},
publisher = {Prospect Press},
year = 2018,
address = {Burlington, VT},
edition = 1,
isbn = {978-1-943153-32-9}
}

APA:

Hall, B. R. & Slonka, K. J. (2020). Assembly Programming and Computer Architecture for Software Engineers (2nd ed.). Burlington, VT: Prospect Press.

Hall, B. R. & Slonka, K. J. (2018). Assembly Programming and Computer Architecture for Software Engineers. Burlington, VT: Prospect Press.

Important Notes

• If you are using macOS High Sierra (10.3) and XCode 9 or later (very likely), you will discover that the i386 architecture is deprecated, and you must use x86_64. We have provided both 32-bit and 64-bit programs where possible but we recommend Edition 2 that has a 64-bit focus. The macOS 10.14 SDK and later do not support 32-bit applications. If you want to write 32-bit programs for i386 on macOS, Xcode 9.4 or earlier is required.

Book

• Why learn Assembly? Is it even used anymore?
• Why x86? Is it too complex for students?
• Why have code for multiple assemblers? Is it confusing?
• Why no custom software (e.g., libraries, macros, environments)?
• Is the GAS and Clang/LLVM code for macOS or Linux?
• What if a web link in the book is broken? / Is there a place with all active web links?
• What if students or instructors want to be able to perform console I/O before Chapter 6 and/or Chapter 10?
• Are there various syntax examples of the Edition 1, Chapter 6 detailed cdecl walkthough?
• Are there various syntax examples of the Edition 2, Chapter 6 detailed x64 walkthough?(Coming Soon!)
• Which provider should I choose for the eBook?

Teaching

• How do the authors pace a semester using the text? / Is there an example course outline?
• Chapter Highlights - What is most important, what do students typically struggle with, and what should students not forget for each chapter?

Programming

• How do I assemble and link on Linux?
• How do I assemble and link on macOS (Terminal)?
• Do I use the .globl or .global directive for main in GAS?
• How do I use GDB or LLDB for command-line debugging?

• Chapter 3, p. 45, Programming Note:
  Incorrect: "The program would expect one piece of data from the user (weight in pounds) and would multiply pounds..."
  Correct: "The program would expect one piece of data from the user (weight in pounds) and would divide pounds..."
• Chapter 3, p. 53, Program 3.2, GAS: Before syscall and .end, the line movl $1, %eax needs removed. This is correct in the repository.
• Chapter 4, p. 62, Addition and Subtraction, GAS DECS example:
  DECS M%rip)/%R should be DECS M%(rip)/%R
• Chapter 6, p. 109, Implementations: A snipped of text from Chapter 12 was mistakenly placed in the final paragraph on page 109 during copy editing. The final two sentences should say: "We also compare cdecl, stdcall, and fastcall conventions in 32-bit. All code examples in this section were written in C++ using Xcode."
• Chapter 8, p. 139, Programming Note: Clarification that FSAVE/FNSAVE first saves the FPU state and then clears the registers.

Edition 1 Samples

• Preface
• Chapter 3: Assembly and Syntax Fundamentals
• Appendix A: Assembly Translation
• Appendix B: Environment Setup
• Appendix E: Linking Assembly and C++
• Appendix I: Intrinsics

Edition 1 Errata

• Chapter 4, p. 76, Program 4.4 - NASM: the line mov eax, array should be mov eax, [array]. Fixed in repository.
• Chapter 5, p. 95, Code Review: JNG description should be "Jump if not greater (signed)". This is correct on p. 88.
• Chapter 6, p. 98, 8th bullet point:
  Incorrect: "The least significant byte is stored at the start of the address (higher) and the most significant byte is stored at the end (lower)."
  Correct: "The least significant byte is stored at the start of the address (lower physcial address) and the most significant byte is stored at the end (higher physical address)."
• Chapter 6, pp. 102-105, Figures 6.2 - 6.6: the line under Instructions in memory 0x1fa7: int $-0x80 was the disassembly visual output (and a bug) in versions of Xcode/LLVM at the time of writing the 1st Edition. The negative sign is incorrect. The bug has since been fixed and the figures will be updated in the next edition update to 0x1fa7: int $0x80.
• Chapter 7, p. 122, CMPS (si and di registers flipped):
  Incorrect: "CMPS compares each corresponding character by performing an implicit subtraction of the character referenced by (r/e)di from the character referenced by (r/e)si..."
  Correct: "CMPS compares each corresponding character by performing an implicit subtraction of the character referenced by (r/e)si from the character referenced by (r/e)di..."

We are very happy to answer any questions or consider suggestions you might have about the text. Just email one of us!
Brian (author) or Beth (publisher)