3 ms·
It's a great article but this drove me nuts: DON'T USE FUCKING AT&T ASSEMBLY SYNTAX. Literally everyone uses Intel syntax, except in those situations where th
by bitwize 11y ago
It's a great article but this drove me nuts:
DON'T USE FUCKING AT&T ASSEMBLY SYNTAX.
Literally everyone uses Intel syntax, except in those situations where they are forced to use AT&T syntax (inline assembly in C on Unix, somehow your box doesn't have NASM). Using AT&T syntax for examples just confuses people. Write assembler the right way. Destination, source. Come on.
- binarycrusader 11y agoNot only is the all caps and profanity uncalled for here, but the unfounded assertion that "everyone" uses "Intel syntax" is wrong. The Solaris assembler as one example, uses the "AT&T syntax". Also, this is reflected in older UNIX apis such as bcopy which use src, dest. Personally, I always preferred src,dest over dest,src but as long as the language is consistent I don't care.
- chrisseaton 11y agoThe default output format of HotSpot is AT&T. The default output format of GCC is AT&T. The default output format of Clang is AT&T. Tools like the universal compiler output viewer https://gcc.godbolt.org https://gcc.godbolt.org use AT&T by default. Intel isn't the universally accepted format you think it is. I'm a professional VM researcher and I use AT&T more often than Intel. In fact I most often see Intel when reading Intel documentation. You're shouting about nothing more than empirical than tabs vs spaces, and even then I think your side is actually in a minority.
- deleted 11y ago[deleted]