You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the greatest pains in reading x86 assembler code is deducing what syntax is going on, AT&T or Intel. This is not a simple matter of style: the order of operands is reversed, making simple extended asm statements such as mov cr3, %0 ambiguous.
Recently released clang 14 allows defining the syntax for inline asm with -masm=syntax, like gcc does. Let's use that to normalize all inline asm to Intel syntax.
In case we return to assembler source files, .intel_syntax is already supported.
The text was updated successfully, but these errors were encountered:
One of the greatest pains in reading x86 assembler code is deducing what syntax is going on, AT&T or Intel. This is not a simple matter of style: the order of operands is reversed, making simple extended asm statements such as
mov cr3, %0
ambiguous.Recently released clang 14 allows defining the syntax for inline asm with
-masm=syntax
, like gcc does. Let's use that to normalize all inline asm to Intel syntax.In case we return to assembler source files,
.intel_syntax
is already supported.The text was updated successfully, but these errors were encountered: