print executable path for cargo build --bench

[cathaysia]

Problem

If it's possible print executable path when build a benchmark? After building the benchmark, I will use perf to run it. But I find it very troublesome to find its path.

Proposed Solution

No response

Notes

No response

[epage]

This can seem obvious to do but the problem it can run into is scale. A cargo build --release --bench foo is one thing. A cargo build --workspace --all-targets is another. Users are pretty sensitive to how much we output. For example, in #12859 we started reporting the paths to generated documentation but collapsed that down (#13557) based on feedback (#13336). In #8889, we are talking about reducing even further how much output we leave on the screen.

[weihanglo]

The executable path is already available through the --no-run flag:

$ cargo bench --no-run
   Compiling foo v0.1.0 (/projects/foo)
    Finished `bench` profile [optimized] target(s) in 0.16s
  Executable benches/x.rs (target/release/deps/x-8870b9bf4b903a7f)

The target/release/deps/x-8870b9bf4b903a7f is the executable. Note that the Executable status message is not a programmable output. For programmable usage, check --message-format=json.

See also #1924, which looks for deterministic filenames for test targets (benchmarks are in the same category).

Going to close this, Cargo already provides executable paths for both human and machine. If there is anything wrong, add comments below!