about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src/coverageinfo/mod.rs
diff options
context:
space:
mode:
author许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com>2024-04-30 19:29:52 +0100
committerGitHub <noreply@github.com>2024-04-30 19:29:52 +0100
commit9ef81e0146d9444749b3416da4bf2fdc5e99d2d7 (patch)
tree415e6fd12c7079526d103b42d551068af3ac62ec /compiler/rustc_codegen_llvm/src/coverageinfo/mod.rs
parent4b6c1918ee13d5e1f7f24037eb6f21dbd95fce08 (diff)
parent7a5038fb4996a4a36d3625c39d04acf27c06d49b (diff)
downloadrust-9ef81e0146d9444749b3416da4bf2fdc5e99d2d7.tar.gz
rust-9ef81e0146d9444749b3416da4bf2fdc5e99d2d7.zip
Rollup merge of #124553 - ferrocene:pa-cargo-git-info, r=onur-ozkan
Write `git-commit-{sha,info}` for Cargo in source tarballs

Right now Cargo doesn't populate the commit hash or date in its version output when it's built from the plain source tarball. That's because we don't include the git information for it, and Cargo's build script doesn't pick it up.

This PR *partially* solves the problem by storing the git information for Cargo in `src/tools/cargo` in the plain source tarball. We store separate information because even when built in CI Cargo uses its own git information rather than Rust's.

This PR will also require a change in the Cargo repository to consume this information (https://github.com/rust-lang/cargo/pull/13832), but it doesn't have to be blocked on the Cargo PR being merged.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/coverageinfo/mod.rs')
0 files changed, 0 insertions, 0 deletions