-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo-objdump
, cargo-size
, etc.
#51
Comments
Adding to the epoch 2018 milestone as discussed in yesterday's meeting |
Can we also add |
When was the last time you needed |
@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, |
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. |
I have implemented step 0 in https://github.com/japaric/cargo-binutils |
The Let's discuss the final UI we want for the Cargo subcommands in the |
Triage
2018-06-29
The
llvm-tools
rustup component now exists andcargo-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.Once #50 is accepted / implemented it would be nice to have wrapper over e.g.
llvm-objdump
forconvenience. The wrapper would take care of passing
-triple=$target
tollvm-objdump
, demanglingthe output, passing the path to the binary to
llvm-objdump
, etc.We don't have to wait until #50 is implemented though; we can start prototyping on top of
arm-none-eabi-objdump
.Tasks
Define what kind of user interface we want. To be done in the cargo-binutils repository.
Prototypecargo-objdump
,cargo-size
, etc. on top ofarm-none-eabi
binutilsMake
cargo-objdump
et al. use LLVM binutils once Ship llvm binutils with the Rust toolchain #50 is implemented.Originally discussed in #43 but I think this more in line with #44
cc @thejpster
The text was updated successfully, but these errors were encountered: