Only load the feature list once in the entire resolver#158263
Conversation
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Only load the feature list once in the entire resolver
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (4063797): comparison URL. Overall result: no relevant changes - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @rustbot label: -S-waiting-on-perf -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary -3.0%, secondary 0.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -1.6%, secondary -1.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 505.379s -> 504.697s (-0.13%) |
| /// Stores `#[diagnostic::on_unknown]` attributes placed on module declarations. | ||
| on_unknown_data: FxHashMap<LocalDefId, OnUnknownData>, | ||
| on_unknown_data: FxHashMap<LocalDefId, OnUnknownData> = default::fx_hash_map(), | ||
| pub features: &'tcx Features, |
There was a problem hiding this comment.
| pub features: &'tcx Features, | |
| features: &'tcx Features, |
Nothing else in Resolver is public, rustc_interface can probably survive calling tcx.features() one more time.
There was a problem hiding this comment.
yea 😅 that was a bit overkill
|
r=me with #158263 (comment) addressed. |
|
Reminder, once the PR becomes ready for a review, use |
|
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. |
This comment has been minimized.
This comment has been minimized.
|
@bors r=petrochenkov rollup |
Only load the feature list once in the entire resolver I saw that a bunch of code in ast validation and other early logic just had the features query called once and stored the result. Let's see what the resolver does with that.
Only load the feature list once in the entire resolver I saw that a bunch of code in ast validation and other early logic just had the features query called once and stored the result. Let's see what the resolver does with that.
I saw that a bunch of code in ast validation and other early logic just had the features query called once and stored the result. Let's see what the resolver does with that.