Tracking Issue for `-Z remap-cwd-prefix`

[ehuss]

This is a tracking issue for -Z remap-cwd-prefix which rewrites absolute paths in the current directory to the given value.

• Docs: https://doc.rust-lang.org/nightly/unstable-book/compiler-flags/remap-cwd-prefix.html
• Implementation: Introduce -Z remap-cwd-prefix switch #87320
• Original issue: Reproducible outputs without build-environment-specific command lines #87325
• MCP: Reproducible command line + determinism compiler-team#450

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Unresolved Questions

• What is the relationship with RFC 3127?
• Will this always be defined to be the same as --remap-path-prefix=$(pwd)=VALUE? That is, what gets remapped? Debug info, backtraces, compiler macros, coverage data, etc? What will happen if RFC 3127 results in separate mapping flags?
• How does this interact with --remap-path-scope?

Implementation history

• Introduce -Z remap-cwd-prefix switch #87320

[fangism]

-Zremap-cwd-prefix=. has been working well for me. We no longer see build environment paths in the strings of the resulting crates and executables.

[cristifalcas]

When will this go to stable flags?