AT&T assembly syntax

Raised as a usability problem by 7 people on Hacker News over 15 years (2010–2024), in 5 threads.

People raised many different problems with AT&T assembly syntax, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 5 complaints

Unclear which operand is compared, so the jump condition direction is confusing to read2024-06-09
Syntax is bolted on and confusing, with many special cases that don't transfer well2024-06-09
Comparison operand order is extremely confusing to reason about2022-11-13
Operand order reversed and size suffixes required, confusing to read and write2012-09-06
Operand order feels unintuitive, and immediate operands need annoying $ prefixes2010-09-06