2020-02-20 03:19:48 -06:00
|
|
|
error: requires at least a template string argument
|
|
|
|
|
--> $DIR/parse-error.rs:9:9
|
|
|
|
|
|
|
|
|
|
|
LL | asm!();
|
|
|
|
|
| ^^^^^^^
|
|
|
|
|
|
|
|
|
|
error: asm template must be a string literal
|
|
|
|
|
--> $DIR/parse-error.rs:11:14
|
|
|
|
|
|
|
|
|
|
|
LL | asm!(foo);
|
|
|
|
|
| ^^^
|
|
|
|
|
|
|
|
|
|
error: expected token: `,`
|
|
|
|
|
--> $DIR/parse-error.rs:13:19
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("{}" foo);
|
|
|
|
|
| ^^^ expected `,`
|
|
|
|
|
|
asm: Allow multiple template strings; interpret them as newline-separated
Allow the `asm!` macro to accept a series of template arguments, and
interpret them as if they were concatenated with a '\n' between them.
This allows writing an `asm!` where each line of assembly appears in a
separate template string argument.
This syntax makes it possible for rustfmt to reliably format and indent
each line of assembly, without risking changes to the inside of a
template string. It also avoids the complexity of having the user
carefully format and indent a multi-line string (including where to put
the surrounding quotes), and avoids the extra indentation and lines of a
call to `concat!`.
For example, rewriting the second example from the [blog post on the new
inline assembly
syntax](https://blog.rust-lang.org/inside-rust/2020/06/08/new-inline-asm.html)
using multiple template strings:
```rust
fn main() {
let mut bits = [0u8; 64];
for value in 0..=1024u64 {
let popcnt;
unsafe {
asm!(
" popcnt {popcnt}, {v}",
"2:",
" blsi rax, {v}",
" jz 1f",
" xor {v}, rax",
" tzcnt rax, rax",
" stosb",
" jmp 2b",
"1:",
v = inout(reg) value => _,
popcnt = out(reg) popcnt,
out("rax") _, // scratch
inout("rdi") bits.as_mut_ptr() => _,
);
}
println!("bits of {}: {:?}", value, &bits[0..popcnt]);
}
}
```
Note that all the template strings must appear before all other
arguments; you cannot, for instance, provide a series of template
strings intermixed with the corresponding operands.
In order to get srcloc mappings right for macros that generate
multi-line string literals, create one line_span for each
line in the string literal, each pointing to the macro.
Make `rustc_parse_format::Parser::curarg` `pub`, so that we can
propagate it from one template string argument to the next.
2020-06-15 01:33:55 -05:00
|
|
|
error: expected operand, options, or additional template string
|
2020-02-20 03:19:48 -06:00
|
|
|
--> $DIR/parse-error.rs:15:20
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("{}", foo);
|
asm: Allow multiple template strings; interpret them as newline-separated
Allow the `asm!` macro to accept a series of template arguments, and
interpret them as if they were concatenated with a '\n' between them.
This allows writing an `asm!` where each line of assembly appears in a
separate template string argument.
This syntax makes it possible for rustfmt to reliably format and indent
each line of assembly, without risking changes to the inside of a
template string. It also avoids the complexity of having the user
carefully format and indent a multi-line string (including where to put
the surrounding quotes), and avoids the extra indentation and lines of a
call to `concat!`.
For example, rewriting the second example from the [blog post on the new
inline assembly
syntax](https://blog.rust-lang.org/inside-rust/2020/06/08/new-inline-asm.html)
using multiple template strings:
```rust
fn main() {
let mut bits = [0u8; 64];
for value in 0..=1024u64 {
let popcnt;
unsafe {
asm!(
" popcnt {popcnt}, {v}",
"2:",
" blsi rax, {v}",
" jz 1f",
" xor {v}, rax",
" tzcnt rax, rax",
" stosb",
" jmp 2b",
"1:",
v = inout(reg) value => _,
popcnt = out(reg) popcnt,
out("rax") _, // scratch
inout("rdi") bits.as_mut_ptr() => _,
);
}
println!("bits of {}: {:?}", value, &bits[0..popcnt]);
}
}
```
Note that all the template strings must appear before all other
arguments; you cannot, for instance, provide a series of template
strings intermixed with the corresponding operands.
In order to get srcloc mappings right for macros that generate
multi-line string literals, create one line_span for each
line in the string literal, each pointing to the macro.
Make `rustc_parse_format::Parser::curarg` `pub`, so that we can
propagate it from one template string argument to the next.
2020-06-15 01:33:55 -05:00
|
|
|
| ^^^ expected operand, options, or additional template string
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
error: expected `(`, found `foo`
|
|
|
|
|
--> $DIR/parse-error.rs:17:23
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("{}", in foo);
|
|
|
|
|
| ^^^ expected `(`
|
|
|
|
|
|
|
|
|
|
error: expected `)`, found `foo`
|
|
|
|
|
--> $DIR/parse-error.rs:19:27
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("{}", in(reg foo));
|
|
|
|
|
| ^^^ expected `)`
|
|
|
|
|
|
|
|
|
|
error: expected expression, found end of macro arguments
|
|
|
|
|
--> $DIR/parse-error.rs:21:27
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("{}", in(reg));
|
|
|
|
|
| ^ expected expression
|
|
|
|
|
|
|
|
|
|
error: expected register class or explicit register
|
|
|
|
|
--> $DIR/parse-error.rs:23:26
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("{}", inout(=) foo => bar);
|
|
|
|
|
| ^
|
|
|
|
|
|
|
|
|
|
error: expected expression, found end of macro arguments
|
|
|
|
|
--> $DIR/parse-error.rs:25:37
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("{}", inout(reg) foo =>);
|
|
|
|
|
| ^ expected expression
|
|
|
|
|
|
|
|
|
|
error: expected one of `!`, `,`, `.`, `::`, `?`, `{`, or an operator, found `=>`
|
|
|
|
|
--> $DIR/parse-error.rs:27:32
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("{}", in(reg) foo => bar);
|
|
|
|
|
| ^^ expected one of 7 possible tokens
|
|
|
|
|
|
|
|
|
|
error: argument to `sym` must be a path expression
|
|
|
|
|
--> $DIR/parse-error.rs:29:24
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("{}", sym foo + bar);
|
|
|
|
|
| ^^^^^^^^^
|
|
|
|
|
|
2020-05-01 17:59:15 -05:00
|
|
|
error: expected one of `)`, `att_syntax`, `nomem`, `noreturn`, `nostack`, `preserves_flags`, `pure`, or `readonly`, found `foo`
|
2020-02-20 03:19:48 -06:00
|
|
|
--> $DIR/parse-error.rs:31:26
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("", options(foo));
|
2020-05-01 17:59:15 -05:00
|
|
|
| ^^^ expected one of 8 possible tokens
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
error: expected one of `)` or `,`, found `foo`
|
|
|
|
|
--> $DIR/parse-error.rs:33:32
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("", options(nomem foo));
|
|
|
|
|
| ^^^ expected one of `)` or `,`
|
|
|
|
|
|
2020-05-01 17:59:15 -05:00
|
|
|
error: expected one of `)`, `att_syntax`, `nomem`, `noreturn`, `nostack`, `preserves_flags`, `pure`, or `readonly`, found `foo`
|
2020-02-20 03:19:48 -06:00
|
|
|
--> $DIR/parse-error.rs:35:33
|
|
|
|
|
|
|
|
|
|
|
LL | asm!("", options(nomem, foo));
|
2020-05-01 17:59:15 -05:00
|
|
|
| ^^^ expected one of 8 possible tokens
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
error: arguments are not allowed after options
|
2020-06-10 20:21:22 -05:00
|
|
|
--> $DIR/parse-error.rs:37:31
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
|
LL | asm!("{}", options(), const foo);
|
|
|
|
|
| --------- ^^^^^^^^^ argument
|
|
|
|
|
| |
|
|
|
|
|
| previous options
|
|
|
|
|
|
|
|
|
|
error: duplicate argument named `a`
|
2021-04-05 23:50:55 -05:00
|
|
|
--> $DIR/parse-error.rs:40:36
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
|
LL | asm!("{a}", a = const foo, a = const bar);
|
|
|
|
|
| ------------- ^^^^^^^^^^^^^ duplicate argument
|
|
|
|
|
| |
|
|
|
|
|
| previously here
|
|
|
|
|
|
|
|
|
|
error: argument never used
|
2021-04-05 23:50:55 -05:00
|
|
|
--> $DIR/parse-error.rs:40:36
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
|
LL | asm!("{a}", a = const foo, a = const bar);
|
|
|
|
|
| ^^^^^^^^^^^^^ argument never used
|
2020-06-10 19:27:48 -05:00
|
|
|
|
|
|
|
|
|
= help: if this argument is intentionally unused, consider using it in an asm comment: `"/* {1} */"`
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
error: explicit register arguments cannot have names
|
2021-04-05 23:50:55 -05:00
|
|
|
--> $DIR/parse-error.rs:45:18
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
|
LL | asm!("", a = in("eax") foo);
|
|
|
|
|
| ^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
|
|
|
error: named arguments cannot follow explicit register arguments
|
2021-04-05 23:50:55 -05:00
|
|
|
--> $DIR/parse-error.rs:47:36
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
|
LL | asm!("{a}", in("eax") foo, a = const bar);
|
|
|
|
|
| ------------- ^^^^^^^^^^^^^ named argument
|
|
|
|
|
| |
|
|
|
|
|
| explicit register argument
|
|
|
|
|
|
|
|
|
|
error: named arguments cannot follow explicit register arguments
|
2021-04-05 23:50:55 -05:00
|
|
|
--> $DIR/parse-error.rs:50:36
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
|
LL | asm!("{a}", in("eax") foo, a = const bar);
|
|
|
|
|
| ------------- ^^^^^^^^^^^^^ named argument
|
|
|
|
|
| |
|
|
|
|
|
| explicit register argument
|
|
|
|
|
|
|
|
|
|
error: positional arguments cannot follow named arguments or explicit register arguments
|
2021-04-05 23:50:55 -05:00
|
|
|
--> $DIR/parse-error.rs:53:36
|
2020-02-20 03:19:48 -06:00
|
|
|
|
|
|
|
|
|
LL | asm!("{1}", in("eax") foo, const bar);
|
|
|
|
|
| ------------- ^^^^^^^^^ positional argument
|
|
|
|
|
| |
|
|
|
|
|
| explicit register argument
|
|
|
|
|
|
asm: Allow multiple template strings; interpret them as newline-separated
Allow the `asm!` macro to accept a series of template arguments, and
interpret them as if they were concatenated with a '\n' between them.
This allows writing an `asm!` where each line of assembly appears in a
separate template string argument.
This syntax makes it possible for rustfmt to reliably format and indent
each line of assembly, without risking changes to the inside of a
template string. It also avoids the complexity of having the user
carefully format and indent a multi-line string (including where to put
the surrounding quotes), and avoids the extra indentation and lines of a
call to `concat!`.
For example, rewriting the second example from the [blog post on the new
inline assembly
syntax](https://blog.rust-lang.org/inside-rust/2020/06/08/new-inline-asm.html)
using multiple template strings:
```rust
fn main() {
let mut bits = [0u8; 64];
for value in 0..=1024u64 {
let popcnt;
unsafe {
asm!(
" popcnt {popcnt}, {v}",
"2:",
" blsi rax, {v}",
" jz 1f",
" xor {v}, rax",
" tzcnt rax, rax",
" stosb",
" jmp 2b",
"1:",
v = inout(reg) value => _,
popcnt = out(reg) popcnt,
out("rax") _, // scratch
inout("rdi") bits.as_mut_ptr() => _,
);
}
println!("bits of {}: {:?}", value, &bits[0..popcnt]);
}
}
```
Note that all the template strings must appear before all other
arguments; you cannot, for instance, provide a series of template
strings intermixed with the corresponding operands.
In order to get srcloc mappings right for macros that generate
multi-line string literals, create one line_span for each
line in the string literal, each pointing to the macro.
Make `rustc_parse_format::Parser::curarg` `pub`, so that we can
propagate it from one template string argument to the next.
2020-06-15 01:33:55 -05:00
|
|
|
error: expected one of `const`, `in`, `inlateout`, `inout`, `lateout`, `options`, `out`, or `sym`, found `""`
|
2021-04-05 23:50:55 -05:00
|
|
|
--> $DIR/parse-error.rs:56:29
|
asm: Allow multiple template strings; interpret them as newline-separated
Allow the `asm!` macro to accept a series of template arguments, and
interpret them as if they were concatenated with a '\n' between them.
This allows writing an `asm!` where each line of assembly appears in a
separate template string argument.
This syntax makes it possible for rustfmt to reliably format and indent
each line of assembly, without risking changes to the inside of a
template string. It also avoids the complexity of having the user
carefully format and indent a multi-line string (including where to put
the surrounding quotes), and avoids the extra indentation and lines of a
call to `concat!`.
For example, rewriting the second example from the [blog post on the new
inline assembly
syntax](https://blog.rust-lang.org/inside-rust/2020/06/08/new-inline-asm.html)
using multiple template strings:
```rust
fn main() {
let mut bits = [0u8; 64];
for value in 0..=1024u64 {
let popcnt;
unsafe {
asm!(
" popcnt {popcnt}, {v}",
"2:",
" blsi rax, {v}",
" jz 1f",
" xor {v}, rax",
" tzcnt rax, rax",
" stosb",
" jmp 2b",
"1:",
v = inout(reg) value => _,
popcnt = out(reg) popcnt,
out("rax") _, // scratch
inout("rdi") bits.as_mut_ptr() => _,
);
}
println!("bits of {}: {:?}", value, &bits[0..popcnt]);
}
}
```
Note that all the template strings must appear before all other
arguments; you cannot, for instance, provide a series of template
strings intermixed with the corresponding operands.
In order to get srcloc mappings right for macros that generate
multi-line string literals, create one line_span for each
line in the string literal, each pointing to the macro.
Make `rustc_parse_format::Parser::curarg` `pub`, so that we can
propagate it from one template string argument to the next.
2020-06-15 01:33:55 -05:00
|
|
|
|
|
|
|
|
|
LL | asm!("", options(), "");
|
|
|
|
|
| ^^ expected one of 8 possible tokens
|
|
|
|
|
|
|
|
|
|
error: expected one of `const`, `in`, `inlateout`, `inout`, `lateout`, `options`, `out`, or `sym`, found `"{}"`
|
2021-04-05 23:50:55 -05:00
|
|
|
--> $DIR/parse-error.rs:58:33
|
asm: Allow multiple template strings; interpret them as newline-separated
Allow the `asm!` macro to accept a series of template arguments, and
interpret them as if they were concatenated with a '\n' between them.
This allows writing an `asm!` where each line of assembly appears in a
separate template string argument.
This syntax makes it possible for rustfmt to reliably format and indent
each line of assembly, without risking changes to the inside of a
template string. It also avoids the complexity of having the user
carefully format and indent a multi-line string (including where to put
the surrounding quotes), and avoids the extra indentation and lines of a
call to `concat!`.
For example, rewriting the second example from the [blog post on the new
inline assembly
syntax](https://blog.rust-lang.org/inside-rust/2020/06/08/new-inline-asm.html)
using multiple template strings:
```rust
fn main() {
let mut bits = [0u8; 64];
for value in 0..=1024u64 {
let popcnt;
unsafe {
asm!(
" popcnt {popcnt}, {v}",
"2:",
" blsi rax, {v}",
" jz 1f",
" xor {v}, rax",
" tzcnt rax, rax",
" stosb",
" jmp 2b",
"1:",
v = inout(reg) value => _,
popcnt = out(reg) popcnt,
out("rax") _, // scratch
inout("rdi") bits.as_mut_ptr() => _,
);
}
println!("bits of {}: {:?}", value, &bits[0..popcnt]);
}
}
```
Note that all the template strings must appear before all other
arguments; you cannot, for instance, provide a series of template
strings intermixed with the corresponding operands.
In order to get srcloc mappings right for macros that generate
multi-line string literals, create one line_span for each
line in the string literal, each pointing to the macro.
Make `rustc_parse_format::Parser::curarg` `pub`, so that we can
propagate it from one template string argument to the next.
2020-06-15 01:33:55 -05:00
|
|
|
|
|
|
|
|
|
LL | asm!("{}", in(reg) foo, "{}", out(reg) foo);
|
|
|
|
|
| ^^^^ expected one of 8 possible tokens
|
|
|
|
|
|
|
|
|
|
error: asm template must be a string literal
|
2021-04-05 23:50:55 -05:00
|
|
|
--> $DIR/parse-error.rs:60:14
|
asm: Allow multiple template strings; interpret them as newline-separated
Allow the `asm!` macro to accept a series of template arguments, and
interpret them as if they were concatenated with a '\n' between them.
This allows writing an `asm!` where each line of assembly appears in a
separate template string argument.
This syntax makes it possible for rustfmt to reliably format and indent
each line of assembly, without risking changes to the inside of a
template string. It also avoids the complexity of having the user
carefully format and indent a multi-line string (including where to put
the surrounding quotes), and avoids the extra indentation and lines of a
call to `concat!`.
For example, rewriting the second example from the [blog post on the new
inline assembly
syntax](https://blog.rust-lang.org/inside-rust/2020/06/08/new-inline-asm.html)
using multiple template strings:
```rust
fn main() {
let mut bits = [0u8; 64];
for value in 0..=1024u64 {
let popcnt;
unsafe {
asm!(
" popcnt {popcnt}, {v}",
"2:",
" blsi rax, {v}",
" jz 1f",
" xor {v}, rax",
" tzcnt rax, rax",
" stosb",
" jmp 2b",
"1:",
v = inout(reg) value => _,
popcnt = out(reg) popcnt,
out("rax") _, // scratch
inout("rdi") bits.as_mut_ptr() => _,
);
}
println!("bits of {}: {:?}", value, &bits[0..popcnt]);
}
}
```
Note that all the template strings must appear before all other
arguments; you cannot, for instance, provide a series of template
strings intermixed with the corresponding operands.
In order to get srcloc mappings right for macros that generate
multi-line string literals, create one line_span for each
line in the string literal, each pointing to the macro.
Make `rustc_parse_format::Parser::curarg` `pub`, so that we can
propagate it from one template string argument to the next.
2020-06-15 01:33:55 -05:00
|
|
|
|
|
|
|
|
|
LL | asm!(format!("{{{}}}", 0), in(reg) foo);
|
|
|
|
|
| ^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
2021-02-13 13:52:25 -06:00
|
|
|
= note: this error originates in the macro `format` (in Nightly builds, run with -Z macro-backtrace for more info)
|
asm: Allow multiple template strings; interpret them as newline-separated
Allow the `asm!` macro to accept a series of template arguments, and
interpret them as if they were concatenated with a '\n' between them.
This allows writing an `asm!` where each line of assembly appears in a
separate template string argument.
This syntax makes it possible for rustfmt to reliably format and indent
each line of assembly, without risking changes to the inside of a
template string. It also avoids the complexity of having the user
carefully format and indent a multi-line string (including where to put
the surrounding quotes), and avoids the extra indentation and lines of a
call to `concat!`.
For example, rewriting the second example from the [blog post on the new
inline assembly
syntax](https://blog.rust-lang.org/inside-rust/2020/06/08/new-inline-asm.html)
using multiple template strings:
```rust
fn main() {
let mut bits = [0u8; 64];
for value in 0..=1024u64 {
let popcnt;
unsafe {
asm!(
" popcnt {popcnt}, {v}",
"2:",
" blsi rax, {v}",
" jz 1f",
" xor {v}, rax",
" tzcnt rax, rax",
" stosb",
" jmp 2b",
"1:",
v = inout(reg) value => _,
popcnt = out(reg) popcnt,
out("rax") _, // scratch
inout("rdi") bits.as_mut_ptr() => _,
);
}
println!("bits of {}: {:?}", value, &bits[0..popcnt]);
}
}
```
Note that all the template strings must appear before all other
arguments; you cannot, for instance, provide a series of template
strings intermixed with the corresponding operands.
In order to get srcloc mappings right for macros that generate
multi-line string literals, create one line_span for each
line in the string literal, each pointing to the macro.
Make `rustc_parse_format::Parser::curarg` `pub`, so that we can
propagate it from one template string argument to the next.
2020-06-15 01:33:55 -05:00
|
|
|
|
|
|
|
|
error: asm template must be a string literal
|
2021-04-05 23:50:55 -05:00
|
|
|
--> $DIR/parse-error.rs:62:21
|
asm: Allow multiple template strings; interpret them as newline-separated
Allow the `asm!` macro to accept a series of template arguments, and
interpret them as if they were concatenated with a '\n' between them.
This allows writing an `asm!` where each line of assembly appears in a
separate template string argument.
This syntax makes it possible for rustfmt to reliably format and indent
each line of assembly, without risking changes to the inside of a
template string. It also avoids the complexity of having the user
carefully format and indent a multi-line string (including where to put
the surrounding quotes), and avoids the extra indentation and lines of a
call to `concat!`.
For example, rewriting the second example from the [blog post on the new
inline assembly
syntax](https://blog.rust-lang.org/inside-rust/2020/06/08/new-inline-asm.html)
using multiple template strings:
```rust
fn main() {
let mut bits = [0u8; 64];
for value in 0..=1024u64 {
let popcnt;
unsafe {
asm!(
" popcnt {popcnt}, {v}",
"2:",
" blsi rax, {v}",
" jz 1f",
" xor {v}, rax",
" tzcnt rax, rax",
" stosb",
" jmp 2b",
"1:",
v = inout(reg) value => _,
popcnt = out(reg) popcnt,
out("rax") _, // scratch
inout("rdi") bits.as_mut_ptr() => _,
);
}
println!("bits of {}: {:?}", value, &bits[0..popcnt]);
}
}
```
Note that all the template strings must appear before all other
arguments; you cannot, for instance, provide a series of template
strings intermixed with the corresponding operands.
In order to get srcloc mappings right for macros that generate
multi-line string literals, create one line_span for each
line in the string literal, each pointing to the macro.
Make `rustc_parse_format::Parser::curarg` `pub`, so that we can
propagate it from one template string argument to the next.
2020-06-15 01:33:55 -05:00
|
|
|
|
|
|
|
|
|
LL | asm!("{1}", format!("{{{}}}", 0), in(reg) foo, out(reg) bar);
|
|
|
|
|
| ^^^^^^^^^^^^^^^^^^^^
|
|
|
|
|
|
|
2021-02-13 13:52:25 -06:00
|
|
|
= note: this error originates in the macro `format` (in Nightly builds, run with -Z macro-backtrace for more info)
|
asm: Allow multiple template strings; interpret them as newline-separated
Allow the `asm!` macro to accept a series of template arguments, and
interpret them as if they were concatenated with a '\n' between them.
This allows writing an `asm!` where each line of assembly appears in a
separate template string argument.
This syntax makes it possible for rustfmt to reliably format and indent
each line of assembly, without risking changes to the inside of a
template string. It also avoids the complexity of having the user
carefully format and indent a multi-line string (including where to put
the surrounding quotes), and avoids the extra indentation and lines of a
call to `concat!`.
For example, rewriting the second example from the [blog post on the new
inline assembly
syntax](https://blog.rust-lang.org/inside-rust/2020/06/08/new-inline-asm.html)
using multiple template strings:
```rust
fn main() {
let mut bits = [0u8; 64];
for value in 0..=1024u64 {
let popcnt;
unsafe {
asm!(
" popcnt {popcnt}, {v}",
"2:",
" blsi rax, {v}",
" jz 1f",
" xor {v}, rax",
" tzcnt rax, rax",
" stosb",
" jmp 2b",
"1:",
v = inout(reg) value => _,
popcnt = out(reg) popcnt,
out("rax") _, // scratch
inout("rdi") bits.as_mut_ptr() => _,
);
}
println!("bits of {}: {:?}", value, &bits[0..popcnt]);
}
}
```
Note that all the template strings must appear before all other
arguments; you cannot, for instance, provide a series of template
strings intermixed with the corresponding operands.
In order to get srcloc mappings right for macros that generate
multi-line string literals, create one line_span for each
line in the string literal, each pointing to the macro.
Make `rustc_parse_format::Parser::curarg` `pub`, so that we can
propagate it from one template string argument to the next.
2020-06-15 01:33:55 -05:00
|
|
|
|
2021-04-05 23:50:55 -05:00
|
|
|
error[E0435]: attempt to use a non-constant value in a constant
|
|
|
|
|
--> $DIR/parse-error.rs:37:37
|
|
|
|
|
|
|
|
|
|
|
LL | let mut foo = 0;
|
|
|
|
|
| ---------- help: consider using `const` instead of `let`: `const foo`
|
|
|
|
|
...
|
|
|
|
|
LL | asm!("{}", options(), const foo);
|
|
|
|
|
| ^^^ non-constant value
|
|
|
|
|
|
|
|
|
|
error[E0435]: attempt to use a non-constant value in a constant
|
|
|
|
|
--> $DIR/parse-error.rs:40:31
|
|
|
|
|
|
|
|
|
|
|
LL | let mut foo = 0;
|
|
|
|
|
| ---------- help: consider using `const` instead of `let`: `const foo`
|
|
|
|
|
...
|
|
|
|
|
LL | asm!("{a}", a = const foo, a = const bar);
|
|
|
|
|
| ^^^ non-constant value
|
|
|
|
|
|
|
|
|
|
error[E0435]: attempt to use a non-constant value in a constant
|
|
|
|
|
--> $DIR/parse-error.rs:40:46
|
|
|
|
|
|
|
|
|
|
|
LL | let mut bar = 0;
|
|
|
|
|
| ---------- help: consider using `const` instead of `let`: `const bar`
|
|
|
|
|
...
|
|
|
|
|
LL | asm!("{a}", a = const foo, a = const bar);
|
|
|
|
|
| ^^^ non-constant value
|
|
|
|
|
|
|
|
|
|
error[E0435]: attempt to use a non-constant value in a constant
|
|
|
|
|
--> $DIR/parse-error.rs:47:46
|
|
|
|
|
|
|
|
|
|
|
LL | let mut bar = 0;
|
|
|
|
|
| ---------- help: consider using `const` instead of `let`: `const bar`
|
|
|
|
|
...
|
|
|
|
|
LL | asm!("{a}", in("eax") foo, a = const bar);
|
|
|
|
|
| ^^^ non-constant value
|
|
|
|
|
|
|
|
|
|
error[E0435]: attempt to use a non-constant value in a constant
|
|
|
|
|
--> $DIR/parse-error.rs:50:46
|
|
|
|
|
|
|
|
|
|
|
LL | let mut bar = 0;
|
|
|
|
|
| ---------- help: consider using `const` instead of `let`: `const bar`
|
|
|
|
|
...
|
|
|
|
|
LL | asm!("{a}", in("eax") foo, a = const bar);
|
|
|
|
|
| ^^^ non-constant value
|
|
|
|
|
|
|
|
|
|
error[E0435]: attempt to use a non-constant value in a constant
|
|
|
|
|
--> $DIR/parse-error.rs:53:42
|
|
|
|
|
|
|
|
|
|
|
LL | let mut bar = 0;
|
|
|
|
|
| ---------- help: consider using `const` instead of `let`: `const bar`
|
|
|
|
|
...
|
|
|
|
|
LL | asm!("{1}", in("eax") foo, const bar);
|
|
|
|
|
| ^^^ non-constant value
|
|
|
|
|
|
|
|
|
|
error: aborting due to 31 previous errors
|
2020-02-20 03:19:48 -06:00
|
|
|
|
2021-04-05 23:50:55 -05:00
|
|
|
For more information about this error, try `rustc --explain E0435`.
|
