Relink don't rebuild: add a baseline, sound implementation that can be incrementally improved#155871
Relink don't rebuild: add a baseline, sound implementation that can be incrementally improved#155871susitsm wants to merge 15 commits intorust-lang:mainfrom
Conversation
|
Some changes occurred in compiler/rustc_attr_parsing cc @jdonszelmann, @JonathanBrouwer Some changes occurred in compiler/rustc_hir/src/attrs cc @jdonszelmann, @JonathanBrouwer Some changes occurred in compiler/rustc_passes/src/check_attr.rs |
|
rustbot has assigned @jdonszelmann. Use Why was this reviewer chosen?The reviewer was selected based on:
|
This comment has been minimized.
This comment has been minimized.
0e63248 to
4b676bd
Compare
|
This is a large change, might take me multiple review passes. I'll see if I can do the first today or tomorrow :) |
|
@rustbot author |
|
Reminder, once the PR becomes ready for a review, use |
| let mut public_api_hasher = PublicApiHasher::default(); | ||
| let tcx = self.tcx; | ||
| let mut stats: Vec<(&'static str, usize)> = Vec::with_capacity(32); | ||
|
|
There was a problem hiding this comment.
The encode_crate_deps below should record the public api hash rather than crate hash when doing rdr, right?
There was a problem hiding this comment.
Short answer: you are right, that will improve it while keeping it sound. I will add that to this PR.
Long answer: one of the main goals of RDR is to enable early cutoff, including the public hash of all dependencies goes against that. We should only include public hashes of dependencies we reexport in some way, or better, only include the hash of the part we reexport. Where reexport here can mean pub use, inlinable/generic/const eval mir reachable through local inlinable/generic/const eval mir and some more stuff we are not aware of yet. Doing this correctly and maintainably is likely the single most technically challenging part of getting RDR right.
There was a problem hiding this comment.
changed it to use public_api_hash, added some comments. 044529d
This comment has been minimized.
This comment has been minimized.
4b676bd to
1682f38
Compare
… rmeta without parents)
…end on public_api_hash instead of crate_hash
…tributes for testing
…stc_public_hash_unchanged attributes
…when changing some rmeta encoder functions
1682f38 to
ab0ab17
Compare
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
@rustbot review |
|
Just realized that there is already a soundness hole: the |
| // should be added here as | ||
| // ``` | ||
| // // FIXME do we need this // or a comment about why we need this | ||
| // let _ = my_new_field; |
There was a problem hiding this comment.
this part is outdated now, about the let _ =
| // `hash_crate_root_public_api`" into `encode_my_new_field` | ||
| // 3. Only remove/change what is hashed in a separate PR. Removing items just from the hash | ||
| // should be done with extreme scrutiny. A better way might be to sort the query result | ||
| // in its provider, or filter which values we encode. That also helps with rmeta size. |
There was a problem hiding this comment.
this should maybe be a fixme at the end
| } | ||
| } | ||
|
|
||
| // When changed, make sure to update the hashing in `hash_crate_root_public_api` |
There was a problem hiding this comment.
ideally, we of course made it so the hashing of that and the encoding here share some of the same source. Maybe by implementing a trait, or calling a method here that adds to the RDR hash, or returning a closure, idk. That way you don't have to think about all these comments and nonlocal subtleties
There was a problem hiding this comment.
that, or even a rustc lint at some point that automatically prompts you if you've made a change here and didn't update the other file. not 100% sure yet what the logic there would be, but this, though better, still seems brittle
|
@rustbot author |
View all comments
This PR implemenets a sound but not too useful implementation of relink don't rebuild with the unstable
-Z public-api-hashflag. It currently uses the stable hash of all items in the metadata.The goal is to give a base implementation that can be used for experimentation. It can be incrementally improved over time by removing or stable sorting items. The PR also adds new test attributes
rustc_public_hash_changedandrustc_public_hash_unchangedand an example test using them.What are non-goals for this PR: a useful, optimized implementation of RDR and public api hashing. That has many more challenges which will each require careful review.
A non exhaustive list of the challenges for the feature I ran into while trying to make the hash useful (this should probably go in a tracking issue, but I'm not aware of one)
my_crate::funcprintsprivate functionas the errorcargo check), could use a much simpler hash than codegen, it does not need private types from mir (or any mir at all?)