Skip to content

Commit f77311b

Browse files
authored
Rollup merge of #88812 - gz:patch-1, r=ehuss
Fix typo `option` -> `options`.
2 parents 0055303 + 5d4d3bd commit f77311b

File tree

1 file changed

+1
-1
lines changed
  • src/doc/unstable-book/src/library-features

1 file changed

+1
-1
lines changed

src/doc/unstable-book/src/library-features/asm.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -375,7 +375,7 @@ Any reuse of a named label, local or otherwise, can result in a assembler or lin
375375

376376
As a consequence, you should only use GNU assembler **numeric** [local labels] inside inline assembly code. Defining symbols in assembly code may lead to assembler and/or linker errors due to duplicate symbol definitions.
377377

378-
Moreover, on x86 when using the default intel syntax, due to [an llvm bug], you shouldn't use labels exclusively made of `0` and `1` digits, e.g. `0`, `11` or `101010`, as they may end up being interpreted as binary values. Using `option(att_syntax)` will avoid any ambiguity, but that affects the syntax of the _entire_ `asm!` block.
378+
Moreover, on x86 when using the default intel syntax, due to [an llvm bug], you shouldn't use labels exclusively made of `0` and `1` digits, e.g. `0`, `11` or `101010`, as they may end up being interpreted as binary values. Using `options(att_syntax)` will avoid any ambiguity, but that affects the syntax of the _entire_ `asm!` block.
379379

380380
```rust,allow_fail
381381
#![feature(asm)]

0 commit comments

Comments
 (0)