diff options
| author | Sander de Smalen <sander.desmalen@arm.com> | 2017-12-14 16:09:48 +0000 |
|---|---|---|
| committer | Sander de Smalen <sander.desmalen@arm.com> | 2017-12-14 16:09:48 +0000 |
| commit | 14e36ee5c385a5368b77eea7a6b0ae8cc3bb40c2 (patch) | |
| tree | 2d0a407b79edd9e64341c628292778cd53994fd1 /llvm/lib/CodeGen/ScheduleDAGInstrs.cpp | |
| parent | 3efcfadde4cebf768f56b22a432185eb9502ea41 (diff) | |
| download | bcm5719-llvm-14e36ee5c385a5368b77eea7a6b0ae8cc3bb40c2.tar.gz bcm5719-llvm-14e36ee5c385a5368b77eea7a6b0ae8cc3bb40c2.zip | |
Re-commit: [TableGen] AsmMatcher: Fix bug with reported diagnostic for operand.
Summary:
The generated diagnostic by the AsmMatcher isn't always applicable to the AsmOperand.
This is because the code will only update the diagnostic if it is more
specific than the previous diagnostic. However, when having validated
operands and 'moved on' to a next operand (for some instruction/alias for
which all previous operands are valid), if the diagnostic is InvalidOperand,
than that should be set as the diagnostic, not the more specific message
about a previous operand for some other instruction/alias candidate.
(Re-committed with an extra whitespace in SVEInstrFormats.td to trigger rebuild
of AArch64GenAsmMatcher.inc, since the llvm-clang-x86_64-expensive-checks-win
builder does not seem to rebuild AArch64GenAsmMatcher.inc with the
newly built TableGen due to a missing dependency somewhere (see:
http://lists.llvm.org/pipermail/llvm-dev/2017-December/119555.html))
Reviewers: craig.topper, olista01, rengolin, stoklund
Reviewed By: olista01
Subscribers: javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D40011
llvm-svn: 320711
Diffstat (limited to 'llvm/lib/CodeGen/ScheduleDAGInstrs.cpp')
0 files changed, 0 insertions, 0 deletions
