`cargo-objdump`, `cargo-size`, etc. about wg HOT 8 CLOSED

Adding to the epoch 2018 milestone as discussed in yesterday's meeting

from wg.

Can we also add cargo-dwarfdump [0]

[0] https://llvm.org/docs/CommandGuide/llvm-dwarfdump.html

from wg.

When was the last time you needed dwarfdump and were not developing an LLVM backend?..

from wg.

@m4b wrote cargo-sym which can be used as limited objdump replacement.

from wg.

@dvc94ch I didn't include that tool in the discussion issue I opened (rust-lang/rust#49584). You can bring it up in the comments.

During yesterday's meeting @jcsoo brought up the idea of having a step 0 for these subcommands: a minimal implementation could simply proxy the LLVM tool; for example, cargo nm -- -C path/to/binary would be sugar for $(rustc --print sysroot)/path/to/llvm-nm -C path/to/binary.

from wg.

@m4b wrote cargo-sym which can be used as limited objdump replacement.

Please, no. This would mean that e.g. the OpenRISC LLVM/rustc port that I maintain would be gated on Capstone gaining OpenRISC support before standard rustc tools could be used.

from wg.

During yesterday's meeting @jcsoo brought up the idea of having a step 0 for these subcommands: a minimal implementation could simply proxy the LLVM tool

I have implemented step 0 in https://github.com/japaric/cargo-binutils

from wg.

The llvm-tools rustup component now exists and cargo-binutils is making use of it. Check this announcement for details.

Let's discuss the final UI we want for the Cargo subcommands in the cargo-binutils issue tracker.

from wg.