Closed e00E closed 2 days ago
This linking is done by rustc/llvm so I can't really prevent it. Forbidding lto and setting unreasonably high codegen unit count would help if not for https://github.com/rust-lang/cargo/issues/13672
What I can try is to detect this kind of behavior and make it so your_crate::bar
is displayed alongside the output you get right now either unconditionally or using recursive context flag...
You can pass -c 1
to see the actual implementation of your_crate::bar
included in the additional context.
I have two functions that happen to have the same assembly. In the output of cargo-asm this looks like this:
The assembly for
bar
contains the actual assembly.This is annoying because I would like to see the assembly immediately in
foo
. I do not want to see this output and then have to switch tobar
. Both functions are marked inline-never.I noticed that whether I get the
.set
behavior depends on what the lto setting is. I'm not sure whether that is relevant.