diff options
| author | Adrian Prantl <aprantl@apple.com> | 2017-09-11 22:59:45 +0000 |
|---|---|---|
| committer | Adrian Prantl <aprantl@apple.com> | 2017-09-11 22:59:45 +0000 |
| commit | 7bc1b28291d6fb60cd055c375a1a94fb6ba7c832 (patch) | |
| tree | f5fee3e80360beaef1d85ba3f0e39b93ce68d09a /llvm/test/DebugInfo/Generic/incorrect-variable-debugloc.ll | |
| parent | 50479f60c40106de3fc5a54b572ccc806f79958a (diff) | |
| download | bcm5719-llvm-7bc1b28291d6fb60cd055c375a1a94fb6ba7c832.tar.gz bcm5719-llvm-7bc1b28291d6fb60cd055c375a1a94fb6ba7c832.zip | |
llvm-dwarfdump: Replace -debug-dump=sect option with individual options.
As discussed on llvm-dev in
http://lists.llvm.org/pipermail/llvm-dev/2017-September/117301.html
this changes the command line interface of llvm-dwarfdump to match the
one used by the dwarfdump utility shipping on macOS. In addition to
being shorter to type this format also has the advantage of allowing
more than one section to be specified at the same time.
In a nutshell, with this change
$ llvm-dwarfdump --debug-dump=info
$ llvm-dwarfdump --debug-dump=apple-objc
becomes
$ dwarfdump --debug-info --apple-objc
Differential Revision: https://reviews.llvm.org/D37714
llvm-svn: 312970
Diffstat (limited to 'llvm/test/DebugInfo/Generic/incorrect-variable-debugloc.ll')
| -rw-r--r-- | llvm/test/DebugInfo/Generic/incorrect-variable-debugloc.ll | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/test/DebugInfo/Generic/incorrect-variable-debugloc.ll b/llvm/test/DebugInfo/Generic/incorrect-variable-debugloc.ll index 0cb73afe6f4..c5add6d1cf9 100644 --- a/llvm/test/DebugInfo/Generic/incorrect-variable-debugloc.ll +++ b/llvm/test/DebugInfo/Generic/incorrect-variable-debugloc.ll @@ -1,6 +1,6 @@ ; REQUIRES: object-emission -; RUN: %llc_dwarf -O2 -filetype=obj < %s | llvm-dwarfdump -debug-dump=info - | FileCheck %s +; RUN: %llc_dwarf -O2 -filetype=obj < %s | llvm-dwarfdump -debug-info - | FileCheck %s ; This is a test case that's as reduced as I can get it, though I haven't fully ; understood the mechanisms by which this bug occurs, so perhaps there's further |
