Include (potentially remapped) working dir in crate hash
Fixes #85019 A `SourceFile` created during compilation may have a relative path (e.g. if rustc itself is invoked with a relative path). When we write out crate metadata, we convert all relative paths to absolute paths using the current working direction. However, the working directory is not included in the crate hash. This means that the crate metadata can change while the crate hash remains the same. Among other problems, this can cause a fingerprint mismatch ICE, since incremental compilation uses the crate metadata hash to determine if a foreign query is green. This commit moves the field holding the working directory from `Session` to `Options`, including it as part of the crate hash.
This commit is contained in:
parent
c0490a2dbb
commit
a895069c50
10 changed files with 61 additions and 18 deletions
|
@ -771,7 +771,7 @@ pub fn file_metadata(cx: &CodegenCx<'ll, '_>, source_file: &SourceFile) -> &'ll
|
|||
let hash = Some(&source_file.src_hash);
|
||||
let file_name = Some(source_file.name.prefer_remapped().to_string());
|
||||
let directory = if source_file.is_real_file() && !source_file.is_imported() {
|
||||
Some(cx.sess().working_dir.to_string_lossy(false).to_string())
|
||||
Some(cx.sess().opts.working_dir.to_string_lossy(false).to_string())
|
||||
} else {
|
||||
// If the path comes from an upstream crate we assume it has been made
|
||||
// independent of the compiler's working directory one way or another.
|
||||
|
@ -999,7 +999,7 @@ pub fn compile_unit_metadata(
|
|||
let producer = format!("clang LLVM ({})", rustc_producer);
|
||||
|
||||
let name_in_debuginfo = name_in_debuginfo.to_string_lossy();
|
||||
let work_dir = tcx.sess.working_dir.to_string_lossy(false);
|
||||
let work_dir = tcx.sess.opts.working_dir.to_string_lossy(false);
|
||||
let flags = "\0";
|
||||
let output_filenames = tcx.output_filenames(());
|
||||
let out_dir = &output_filenames.out_directory;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue