llvm-objdump takes foo-bar style flags, while llvm-otool takes foo_bar style
flags. dyld_info was the only exception to that.
Details
Diff Detail
Event Timeline
I picked this option name to match the system tools on macOS, which also use this spelling (but I agree it's inconsistent).
Right, we have llvm-otool which matches the otool flags. None of the other objdump flags match the cctools's option spellings.
I've got nothing against this, although it probably deserves a release note, in case there are any existing users of that spelling and llvm-objdump.
aprantl: I added -dyld_info to llvm-otool instead. Does that work for you?
jhenderson: The flag currently doesn't really do anything, it calls PrintDyldInfo which calls one more function which internally casts everything to (void). So I don't think there are any actual non-test users of this flag, and maybe we can get away without a release notes entry in this case?
Up to you - if you don't think it's needed, that's fine (I don't know anything about its usage or behaviour).
Splitting it this way works for me (although it's still going to be confusing that we have two spellings).