mirror of
https://github.com/pkivolowitz/asm_book.git
synced 2026-06-21 01:56:47 +08:00
88c8f496c4
Closes #22. The alignment chapter's hex dump examples (e.g. "0011 eeff ccdd aabb" for a little-endian long initialized to 0xaabbccddeeff0011) are correct under the default hexdump(1) output convention: bytes grouped into 16-bit little-endian words, each word printed most-significant byte first. But the chapter never told the reader which convention was in use, so a reader reproducing the example with xxd or hexdump -C (both byte-oriented, showing raw memory order) would get a different-looking result and conclude the book had an endianness bug. That is exactly what issue #22 reported, and it is also part of what the #33 filer flagged as "there are no instructions about how to do such a thing" for hex dumps in this chapter. Fix: one new subsection "A Note on Hex Dumps" placed before Example 1, stating the convention explicitly and warning xxd / hexdump -C users that the bytes within each pair will appear swapped relative to the examples. The examples themselves are unchanged; they were already self-consistent under the word-oriented convention. Rejected alternative: rewriting all the examples in byte-oriented (xxd) form. That would have matched what most modern readers reach for, but would also have required regenerating every hex dump in the chapter and losing continuity with any reader who already absorbed the current notation. A single explanatory paragraph is less invasive and teaches the distinction, which is useful in its own right. No test coverage applies; this is prose. |
||
|---|---|---|
| .. | ||
| const | ||
| fizzbuzz | ||
| for | ||
| funcs | ||
| hello_world | ||
| if | ||
| jump_tables | ||
| recursion | ||
| regs | ||
| structs | ||
| while | ||
| hex.md | ||
| hex.pdf | ||
| kickstart.md | ||
| kickstart.pdf | ||