Open
Description
This is the tracking issue for the unstable option -Z src-hash-algorithm
Steps
- Implementation PR Add hash of source files in debug info #69718Adjust documentationStabilization 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?
Metadata
Metadata
Assignees
Labels
Area: Command-line interface (CLI) to the compilerArea: Debugging information in compiled programs (DWARF, PDB, etc.)Blocker: Implemented in the nightly compiler and unstable.Category: An issue tracking the progress of sth. like the implementation of an RFCStatus: There are blocking design concerns.Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
Auto merge of rust-lang#69718 - arlosi:debughash, r=eddyb
est31 commentedon Oct 8, 2020
#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.
Rollup merge of rust-lang#77950 - arlosi:sha256, r=eddyb
Rollup merge of rust-lang#77950 - arlosi:sha256, r=eddyb
pierwill commentedon Oct 13, 2021
Are there documentation changes needed for this? I'd be happy to help!
pierwill commentedon Oct 18, 2021
☝️ @eddyb
arlosi commentedon Oct 18, 2021
@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 commentedon Sep 9, 2022
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