Repository navigation
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.
Move lang item collection to the resolver
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (ee7b1cf): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. @bors rollup=never rustc-perf Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary 1.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 1.5%, secondary -0.3%)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: 489.184s -> 489.805s (0.13%) |
|
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
It probably doesn't matter much where exactly the set of extern crates is walked, in rustc_resolve or later in rustc_passes (from a query)? |
This comment has been minimized.
This comment has been minimized.
90ed939 to
18b002a
Compare
This comment has been minimized.
This comment has been minimized.
|
@rustbot ready addressed the review comments |
This comment has been minimized.
This comment has been minimized.
18b002a to
5221654
Compare
|
@bors r+ |
|
@bors rollup=iffy |
…rochenkov Move lang item collection to the resolver The separate query had to walk the entire ast again, also tracking owners and converting NodeIds to DefIds. I think it's nicer to just do it as part of the resolver. Alternatively we could limit the lang item collection to the local ones and keep the query. Instead of walking the current crate again we'd just take the list from the resolver query just like we take the list from upstream crates.
…rochenkov Move lang item collection to the resolver The separate query had to walk the entire ast again, also tracking owners and converting NodeIds to DefIds. I think it's nicer to just do it as part of the resolver. Alternatively we could limit the lang item collection to the local ones and keep the query. Instead of walking the current crate again we'd just take the list from the resolver query just like we take the list from upstream crates.
…uwer Rollup of 5 perf-sensitive pull requests Successful merges: - #165032 (stdarch subtree update) - #163525 (Move lang item collection to the resolver) - #164234 (New solver opts for `diesel` (part 2)) - #164726 (perf: emit field names as a concatenated string in derive(Debug) for structs) - #164953 (Avoid stdlib's `impl Hash for Discriminant` for stable hashing)
…rochenkov Move lang item collection to the resolver The separate query had to walk the entire ast again, also tracking owners and converting NodeIds to DefIds. I think it's nicer to just do it as part of the resolver. Alternatively we could limit the lang item collection to the local ones and keep the query. Instead of walking the current crate again we'd just take the list from the resolver query just like we take the list from upstream crates.
…uwer Rollup of 5 perf-sensitive pull requests Successful merges: - #163525 (Move lang item collection to the resolver) - #164234 (New solver opts for `diesel` (part 2)) - #164726 (perf: emit field names as a concatenated string in derive(Debug) for structs) - #164953 (Avoid stdlib's `impl Hash for Discriminant` for stable hashing) - #164969 (perf: avoid allocating HashSet in is_distinct check on small SwitchInts)
…rochenkov Move lang item collection to the resolver The separate query had to walk the entire ast again, also tracking owners and converting NodeIds to DefIds. I think it's nicer to just do it as part of the resolver. Alternatively we could limit the lang item collection to the local ones and keep the query. Instead of walking the current crate again we'd just take the list from the resolver query just like we take the list from upstream crates.
This comment has been minimized.
This comment has been minimized.
5221654 to
5156c51
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. |
|
@bors r=petrochenkov |
|
@bors rollup=never |
|
@bors rollup=iffy |
…rochenkov Move lang item collection to the resolver The separate query had to walk the entire ast again, also tracking owners and converting NodeIds to DefIds. I think it's nicer to just do it as part of the resolver. Alternatively we could limit the lang item collection to the local ones and keep the query. Instead of walking the current crate again we'd just take the list from the resolver query just like we take the list from upstream crates.
…uwer Rollup of 7 perf-sensitive pull requests Successful merges: - #163339 (MIR move elimination [5/6]: Storage reconstruction) - #163525 (Move lang item collection to the resolver) - #163928 (do not prefer trivially true candidates with `-Znext-solver` ) - #164341 (Expand an early return case in `coerce_unsized`) - #164484 (Use adaptive sparse encoding for metadata tables) - #164607 (destringlyfy lint infrastructure) - #165160 (New solver opts for diesel (part 3)) > [!WARNING] > This rollup conflicts with pending auto build #165178 and may need to be recreated if the pending build succeeds.
…uwer Rollup of 7 perf-sensitive pull requests Successful merges: - #163339 (MIR move elimination [5/6]: Storage reconstruction) - #163525 (Move lang item collection to the resolver) - #163928 (do not prefer trivially true candidates with `-Znext-solver` ) - #164341 (Expand an early return case in `coerce_unsized`) - #164484 (Use adaptive sparse encoding for metadata tables) - #164607 (destringlyfy lint infrastructure) - #165160 (New solver opts for diesel (part 3)) > [!WARNING] > This rollup conflicts with pending auto build #165178 and may need to be recreated if the pending build succeeds.
…uwer Rollup of 7 perf-sensitive pull requests Successful merges: - #163339 (MIR move elimination [5/6]: Storage reconstruction) - #163525 (Move lang item collection to the resolver) - #163928 (do not prefer trivially true candidates with `-Znext-solver` ) - #164341 (Expand an early return case in `coerce_unsized`) - #164484 (Use adaptive sparse encoding for metadata tables) - #164607 (destringlyfy lint infrastructure) - #165160 (New solver opts for diesel (part 3)) > [!WARNING] > This rollup conflicts with pending auto build #165178 and may need to be recreated if the pending build succeeds.
View all comments
The separate query had to walk the entire ast again, also tracking owners and converting NodeIds to DefIds. I think it's nicer to just do it as part of the resolver.
Alternatively we could limit the lang item collection to the local ones and keep the query. Instead of walking the current crate again we'd just take the list from the resolver query just like we take the list from upstream crates.