Tracking issue for `-Z profile`

Question

Tracking issue for `-Z profile`

alexcrichton opened this issue 8 years ago · 11 comments

This is intended to be a tracking issue for the profiling feature, built on the gcov-style support in LLVM first added in #38608 and later rebased in #42433.

Answer 1 · 2019-12-25T16:02:51.000Z

Triage: not aware of any major move to stabilize this.

Answer 2 · 2020-02-07T13:10:58.000Z

Is it expected that this doesn't work with --release?

Answer 3 · 2020-10-08T21:58:40.000Z

Is there a way to change the path that the tests output to? I want to use this on some code that is cross compiled and needs to run on a device that only has a few writable paths. I'm currently getting this to work by replacing /target/aarch64... with ./arget/aarch64... in the binary since we can't change the length of the string.

I've never worked on the compiler before, but an option for this would be very useful.

Answer 4 · 2024-11-09T06:12:49.000Z

Removed: #131829

Answer 5 · 2024-11-09T13:40:22.000Z

Aw, that's unfortunate.

Answer 6 · 2024-11-09T17:19:08.000Z

@whitequark why so

Answer 7 · 2024-11-09T17:38:12.000Z

As far as I understand there's no replacement?

Answer 8 · 2024-11-09T17:48:50.000Z

was thinking this was for branch coverage, which has since been implemented

Answer 9 · 2024-11-09T18:01:18.000Z

Oh. I missed that then!

Answer 10 · 2024-11-09T21:05:00.000Z

@whitequark Yes, -Cinstrument-coverage should work and supports the llvm-cov style of handling coverage: https://doc.rust-lang.org/nightly/rustc/instrument-coverage.html

Answer 11 · 2024-11-10T20:13:35.000Z

Oh that's fantastic work =^_^=