diff options
author | Nico Weber <thakis@chromium.org> | 2021-04-12 22:31:08 -0400 |
---|---|---|
committer | Nico Weber <thakis@chromium.org> | 2021-04-14 20:12:24 -0400 |
commit | 1035123ac50db21bb2f44f78c040a823d7d064b2 (patch) | |
tree | 52dbfee776e4cdcbdcb41b89b7156866049472c5 /lldb/packages/Python/lldbsuite/test/dotest.py | |
parent | dc1ab590a0527533815aeed0100de54a5f4a4829 (diff) | |
download | llvm-1035123ac50db21bb2f44f78c040a823d7d064b2.zip llvm-1035123ac50db21bb2f44f78c040a823d7d064b2.tar.gz llvm-1035123ac50db21bb2f44f78c040a823d7d064b2.tar.bz2 |
[llvm-objdump] Switch command-line parsing from llvm::cl to OptTable
This is similar to D83530, but for llvm-objdump.
The motivation is the desire to add an `llvm-otool` symlink to
llvm-objdump that behaves like macOS's `otool`, using the same
technique the at llvm-objcopy uses to behave like `strip` (etc).
This change for the most part preserves behavior. In some cases,
it increases compatibility with GNU objdump a bit. For example,
the long options now require two dashes, and the long options
taking arguments for the most part now require a `=` in front
of the value. Exceptions are flags where tests passed the
value separately, for these the separate form is kept as
an alias to the = form.
The one-letter short form args are now joined or separate
and long longer accept a =, which also matches GNU objdump.
cl::opt<>s in libraries now have to be explicitly plumbed
through. This patch does that for --x86-asm-syntax=, but
there's hope that we can remove that again.
Differential Revision: https://reviews.llvm.org/D100433
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/dotest.py')
0 files changed, 0 insertions, 0 deletions