diff options
| author | Oliver Stannard <oliver.stannard@arm.com> | 2017-10-04 09:18:07 +0000 |
|---|---|---|
| committer | Oliver Stannard <oliver.stannard@arm.com> | 2017-10-04 09:18:07 +0000 |
| commit | 5a7aae3a80373a71747b1a4754d81b37fee773c7 (patch) | |
| tree | 6da2cccaa62d76769d86c1e872e8bc4cb657001a /llvm/lib/Support/Parallel.cpp | |
| parent | 3c29bacd43ffd9bb15eebcf1afc12106806030bd (diff) | |
| download | llvm-5a7aae3a80373a71747b1a4754d81b37fee773c7.zip llvm-5a7aae3a80373a71747b1a4754d81b37fee773c7.tar.gz llvm-5a7aae3a80373a71747b1a4754d81b37fee773c7.tar.bz2 | |
[ARM, Asm] Change grammar of immediate operand diagnostics
Currently, our diagnostics for assembly operands are not consistent.
Some start with (for example) "immediate operand must be ...",
and some with "operand must be an immediate ...". I think the latter
form is preferable for a few reasons:
* It's unambiguous that it is referring to the expected type of operand, not
the type the user provided. For example, the user could provide an register
operand, and get a message taking about an operand is if it is already an
immediate, just not in the accepted range.
* It allows us to have a consistent style once we add diagnostics for operands
that could take two forms, for example a label or pc-relative memory operand.
Differential revision: https://reviews.llvm.org/D36689
llvm-svn: 314887
Diffstat (limited to 'llvm/lib/Support/Parallel.cpp')
0 files changed, 0 insertions, 0 deletions