pacak
pacak
All the commands you gave me are failing with rustc/cargo complaining about missing stuff, probably my crosscompilation pipeline is not configured at all, but I managed to reproduce your error...
I thought about it. This only works for instructions that are one word long, but there are instructions that go with prefixes: ``` lock inc word [edi + r10d*4] ```...
> Now that I've typed that all out, possibly the right answer is that these `.cv_file` bits generated from Rust are just wrong and this should be fixed there. Yay...
I pushed a branch called `cursed`, can you check if it solves your problem?
Do you have an example to reproduce the problem?
On x86 this generates a huge table but it goes into a separate section so output is still perfectly readable. Can you post some sample output of how it looks...
> [Here's an example](https://gist.github.com/zesterer/6f692c478e518dc983262a7a9d9c327e). Is that the output from `cargo-show-asm`? Those tables go into separate sections and I expect them not to be displayed by default.
If it dumps in a single line I'd use something like `cargo asm ... --color | less -SR`
Anyway, I don't mind adding something to deal with this issue, but only if it can't be solved with `less` as I shown above.
Whole point of LTO is to optimize the code in a context that is not available when you compile parts separately. Now, by default `cargo-show-asm` asks `rustc` to dump assembly...