[LLVMdev] Looking for ideas on how to make llvm-objdump handle both arm and thumb disassembly from the same object file

Rafael EspĂ­ndola rafael.espindola at gmail.com
Thu Aug 7 07:09:47 PDT 2014


> The implementation of llvm-objdump does have a MachODump.cpp for use with the -m option that I could do the a similar hack otool(1) like hack and special case 32-bit ARM cpus.  And at least it contains the ugliness.  But this does not really help the non -m case and I suspect ELF objects may face a similar problem.

My gut feeling would be to do this first and keep an eye for how to
refactor it when we want to add support for ELF or for things like
mips16.

CCing Eric since he is now the expert on the target/subtarget relationship.

> The other more radical change I was thinking of was maybe changing MachODump.cpp to use the C API.  Then at least this way we would have something in the tree that used this and could actually have test cases.  That could then use the call backs to symbolic operands etc.  But that still could be done with the C++ API using TheTarget->createMCSymbolizer() anyway.

Using the C api seems odd.

> So if any of you have suggestions for a direction for this let me know,
> Kev

Cheers,
Rafael




More information about the llvm-dev mailing list