Remove rustc_query_system#152703
Conversation
It's identical to the one in `rustc_query_impl`.
From `rustc_query_system` to `rustc_middle.` I put it in `graph.rs`, it's one of two files that uses `QuerySideEffect` and seemed as good as anywhere else.
|
The rustc-dev-guide subtree was changed. If this PR only touches the dev guide consider submitting a PR directly to rust-lang/rustc-dev-guide otherwise thank you for updating the dev guide with your changes. cc @BoxyUwU, @jieyouxu, @Kobzol, @tshepang
|
|
|
This comment has been minimized.
This comment has been minimized.
|
Those inline snapshot tests in bootstrap are more annoying to bless; there are instructions at: Lines 222 to 227 in fef627b EDIT: Alternatively, you could hand-edit them from |
|
Once again, let's get the precautionary perf run out of the way early. The failing bootstrap snapshot tests (hopefully) shouldn't matter for this purpose. @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.
It's plumbing to work around lack of access to `rustc_middle`, which is no longer a problem.
Like the previous commit, it's no longer needed.
At this point module `ich` is the only thing left.
|
r=me with fixed tests and acceptable perf. |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (66eb71c): comparison URL. Overall result: no relevant changes - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (secondary 2.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.9%, secondary 2.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 481.396s -> 480.438s (-0.20%) |
8d086e3 to
e9288e7
Compare
|
Tests are passing and perf is neutral. @bors r=Zalathar rollup=maybe |
… r=Zalathar Remove `rustc_query_system` The end point of the PR sequence rust-lang#152160, rust-lang#152419, rust-lang#152516. r? @Zalathar
Rollup of 6 pull requests Successful merges: - #145399 (Unify wording of resolve error) - #152512 (core: Implement feature `float_exact_integer_constants`) - #152661 (Avoid ICE in From/TryFrom diagnostic under -Znext-solver) - #152703 (Remove `rustc_query_system`) - #152727 (`probe_op` silence ambiguity errors if tainted) - #152728 (Port #![default_lib_allocator] to the new attribute parser)
Rollup of 11 pull requests Successful merges: - #152700 (miri subtree update) - #152715 (`rust-analyzer` subtree update) - #151783 (Implement RFC 3678: Final trait methods) - #152512 (core: Implement feature `float_exact_integer_constants`) - #152661 (Avoid ICE in From/TryFrom diagnostic under -Znext-solver) - #152703 (Remove `rustc_query_system`) - #152206 (misc doc improvements) - #152664 (Fix mis-constructed `file_span` when generating scraped examples) - #152698 (Suppress unstable-trait notes under `-Zforce-unstable-if-unmarked`) - #152727 (`probe_op` silence ambiguity errors if tainted) - #152728 (Port #![default_lib_allocator] to the new attribute parser)
The end point of the PR sequence #152160, #152419, #152516.
r? @Zalathar