[llvm] r217985 - [llvm-objdump] clean up test cases now that build bots are green

[Rafael Espíndola]

>> I guess the ideal situation would be to have a llvm-otool and llvm-dyldinfo :-)
>
> I don’t follow why that would be better. Can you elaborate a bit? The current precedent for this sort of thing is things like sniffing argv[0] and using symlinks or something like that if we want different behavior based on how the tool was invoked. For cross-platform testing, a —flavor option will do the trick. This is basically what both the clang driver and LLD do and it seems to work pretty well.

Oh, I don't have an opinion on how a llvm-otool would be implemented.

The point is just that the objective of llvm-objdump is to be a user
tool similar to the system objdump. The command line interface of
otool is sufficiently different that it probably makes sense to have a
llvm-otool instead of just objdump extensions to handle MachO, but
yes, it can be implemented with a symlink and a check of argv[0] (like
llvm-ranlib for example) if that is convenient.

Cheers,
Rafael