Repository navigation
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## preprocessor-entry-decode #2942 +/- ##
=============================================================
+ Coverage 78.60% 78.68% +0.07%
=============================================================
Files 74 74
Lines 44179 44364 +185
=============================================================
+ Hits 34728 34908 +180
- Misses 9451 9456 +5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
sylvestre
force-pushed
the
rust-direct-mode
branch
from
October 24, 2026 16:02
dcd3cbb to
f2fc1c0
Compare
sylvestre
force-pushed
the
rust-direct-mode
branch
from
October 24, 2026 16:05
f2fc1c0 to
1702a91
Compare
sylvestre
force-pushed
the
rust-direct-mode
branch
2 times, most recently
from
October 25, 2026 08:52
3803310 to
0990e77
Compare
sylvestre
marked this pull request as ready for review
October 25, 2026 08:56
sylvestre
force-pushed
the
rust-direct-mode
branch
from
October 25, 2026 13:13
0990e77 to
a7fb045
Compare
sylvestre
force-pushed
the
rust-direct-mode
branch
from
October 25, 2026 13:45
a7fb045 to
a106f24
Compare
sylvestre
force-pushed
the
rust-direct-mode
branch
2 times, most recently
from
October 25, 2026 22:08
e012b60 to
b35987c
Compare
To compute the cache key of a crate, sccache runs `rustc --emit=dep-info` to list its source files and env-deps, and `rustc --print file-names` to list its outputs, even when the compile then hits the cache. The first one parses and expands the whole crate, proc macros included, and was most of the work of a Rust cache hit. The server now remembers what both runs found, and reuses it for a later compile with the same compiler, arguments, working directory, environment, externs, static libraries and target spec, as long as every listed source file still has the same digest and every env-dep the same value. The whole environment is part of that key, except the jobserver variables, so that a proc macro picking its inputs from an untracked variable can only cause a miss. Entries live for the life of the server; nothing is written to the cache. All-hits debug build of sccache (332 Rust crates): wall: 5.7 s -> 3.9 s server-side CPU, including the rustc it runs: 26.3 s -> 4.1 s
sylvestre
force-pushed
the
rust-direct-mode
branch
from
October 25, 2026 22:09
b35987c to
4e4f932
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
rust: reuse dep-info and output lists across compiles of a crate
To compute the cache key of a crate, sccache runs
rustc --emit=dep-infoto list its source files and env-deps, and
rustc --print file-namestolist its outputs, even when the compile then hits the cache. The first one
parses and expands the whole crate, proc macros included, and was most of
the work of a Rust cache hit.
The server now remembers what both runs found, and reuses it for a later
compile with the same compiler, arguments, working directory, environment,
externs, static libraries and target spec, as long as every listed source
file still has the same digest and every env-dep the same value. The whole
environment is part of that key, except the jobserver variables, so that a
proc macro picking its inputs from an untracked variable can only cause a
miss. Entries live for the life of the server; nothing is written to the
cache.
All-hits debug build of sccache (332 Rust crates):
wall: 5.7 s -> 3.9 s
server-side CPU, including the rustc it runs: 26.3 s -> 4.1 s