projects / platform / upstream / llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 014648e) | patch
[llvm-dwarfdump][test] Use verbose output to check expected opcodes
authorJames Henderson <james.henderson@sony.com>
Wed, 20 May 2020 14:29:55 +0000 (15:29 +0100)
committerJames Henderson <james.henderson@sony.com>
Mon, 1 Jun 2020 10:48:02 +0000 (11:48 +0100)
commit7bcde99f7779a71a389e559b7ff2ff6ec43ae004
tree7478aed7890a97bc42142c05712217fc3bccd166tree | snapshot
parent014648e8f27b2f57940844f0170d15b42a497d33commit | diff
[llvm-dwarfdump][test] Use verbose output to check expected opcodes

The debug_line_invalid.test test case was previously using the
interpreted line table dumping to identify which opcodes have been
parsed. This change moves to looking for the expected opcodes
explicitly. This is probably a little clearer and also allows for
testing some cases that wouldn't be easily identifiable from the
interpreted table.

Reviewed by: MaskRay

Differential Revision: https://reviews.llvm.org/D80795
llvm/test/tools/llvm-dwarfdump/X86/debug_line_invalid.test diff | blob | history
Domain: System / Toolchain;