summaryrefslogtreecommitdiffstats
path: root/llvm/test/tools
diff options
context:
space:
mode:
authorKevin Enderby <enderby@apple.com>2017-01-30 20:53:17 +0000
committerKevin Enderby <enderby@apple.com>2017-01-30 20:53:17 +0000
commit98898f2b0283629a03e52950da0007bb82b01ef7 (patch)
tree26b91397faea65c4b97aa78511b652676061febc /llvm/test/tools
parentc94497048434ede852fe3db7870ba97864d8e1bf (diff)
downloadbcm5719-llvm-98898f2b0283629a03e52950da0007bb82b01ef7.tar.gz
bcm5719-llvm-98898f2b0283629a03e52950da0007bb82b01ef7.zip
Change the llvm-obdump(1) behavior with the -macho flag and inappropriate file types.
To better match the old darwin otool(1) behavior, when llvm-obdump(1) is used with the -macho option and the input file is not an object file simply print the file name and this message: foo: is not an object file and continue on to process other input files. Also in this case don’t exit non-zero. This should help in some OSS projects' with autoconf scripts that are expecting the old darwin otool(1) behavior. rdar://26828015 llvm-svn: 293547
Diffstat (limited to 'llvm/test/tools')
-rw-r--r--llvm/test/tools/llvm-objdump/malformed-macho.test5
1 files changed, 3 insertions, 2 deletions
diff --git a/llvm/test/tools/llvm-objdump/malformed-macho.test b/llvm/test/tools/llvm-objdump/malformed-macho.test
index 0bc2ce8e898..924d58a1df2 100644
--- a/llvm/test/tools/llvm-objdump/malformed-macho.test
+++ b/llvm/test/tools/llvm-objdump/malformed-macho.test
@@ -1,2 +1,3 @@
-RUN: not llvm-objdump -macho -s %p/Inputs/malformed-macho.bin 2>&1 | FileCheck %s -check-prefix=MALFORMED
-MALFORMED: The file was not recognized as a valid object file
+RUN: llvm-objdump -macho -private-header %p/Inputs/malformed-macho.bin %p/Inputs/empty.macho-armv7 2>&1 | FileCheck %s -check-prefix=MALFORMED
+MALFORMED: is not an object file
+MALFORMED-NEXT: Mach header
OpenPOWER on IntegriCloud