diff options
| author | bors <bors@rust-lang.org> | 2018-10-10 22:24:48 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-10-10 22:24:48 +0000 |
| commit | f42c510f2f952a6eba80e6448b46e83bfcc04e44 (patch) | |
| tree | d57bb7afe65000a868a8900c04d9cef4d2904e4d /src/libsyntax/parse | |
| parent | 5af0bb83044c3fb43d59ad5f49ee5ae1a293901f (diff) | |
| parent | 3d7476eae1f4903684426835e97ba8f5d337c300 (diff) | |
| download | rust-f42c510f2f952a6eba80e6448b46e83bfcc04e44.tar.gz rust-f42c510f2f952a6eba80e6448b46e83bfcc04e44.zip | |
Auto merge of #54747 - levex:inline-asm-bad-operands, r=nagisa
codegen_llvm: verify that inline assembly operands are scalars Another set of inline assembly fixes. This time let's emit an error message when the operand value cannot be coerced into the operand constraint. Two questions: 1) Should I reuse `E0668` which was introduced in #54568 or just use `E0669` as it stands because they do mean different things, but maybe that's not too user-friendly. Just a thought. 2) The `try_fold` returns the operand which failed to be converted into a scalar value, any suggestions on how to use that in the error message? Thanks!
Diffstat (limited to 'src/libsyntax/parse')
0 files changed, 0 insertions, 0 deletions