Tracking Issue for `-Z src-hash-algorithm`

[arlosi]

This is the tracking issue for the unstable option -Z src-hash-algorithm

Steps

• Implementation PR Add hash of source files in debug info #69718
• Adjust documentation
• Stabilization PR

Unresolved Questions

• Should we have a separate option in the target specification to specify the preferred hash algorithm, or continue to use is_like_msvc?
• Should continue to have a command line option to override the preferred option? Or is it acceptable to require users to create a custom target specification to override the hash algorithm?

[est31]

#73526 has been merged, updating LLVM to 11 and making it possible to support SHA256 as well. I guess for now one still has to give compatibility for older LLVMs though, so one maybe has to place a few cfg's here and there.

[pierwill]

Are there documentation changes needed for this? I'd be happy to help!

[pierwill]

☝️ @eddyb

[arlosi]

@pierwill It is currently documented as an unstable option here: https://doc.rust-lang.org/beta/unstable-book/compiler-flags/src-hash-algorithm.html

I think the next step here would be to make a stabilization PR and adjust the documentation move it to the stable list of codegen options.

[pnkfelix]

Visited during T-compiler backlog bonanza

It sounds like this is either ready to stabilize as is (with a shift from a -Z option to something stable), or it should move into something that is specified as part of of the target specification, and we just aren't even sure which of those modes we want this in for the stable form.

Can we maybe get a summary of the current implementation status, as well as the tradeoffs between those two options, to inform that decision?

@rustbot label: S-tracking-needs-summary