Repository navigation
Conversation
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
…remapping, r=<try> Remap syntax contexts and expansion ids for det. metadata encoding
This comment has been minimized.
This comment has been minimized.
4195a79 to
46ee492
Compare
|
@bors try cancel |
|
Try build cancelled. Cancelled workflows: Hint: if you want to run another try build, you do not need to manually cancel the previous one. Just run |
|
@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.
…remapping, r=<try> Remap syntax contexts and expansion ids for det. metadata encoding
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment was marked as outdated.
This comment was marked as outdated.
07a0f64 to
43e622c
Compare
|
@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.
…remapping, r=<try> Remap syntax contexts and expansion ids for det. metadata encoding
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (a7c6732): comparison URL. Overall result: ❌✅ regressions and improvements - please read:Benchmarking 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. Next, please: If you can, justify the regressions found in this try perf run in writing along with @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 (primary -2.9%, secondary -1.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 11.8%, secondary 2.4%)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: 490.152s -> 495.841s (1.16%) |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (1e274b8): comparison URL. Overall result: ❌✅ regressions and improvements - please read:Benchmarking 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. Next, please: If you can, justify the regressions found in this try perf run in writing along with @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.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 0.8%, secondary 1.6%)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: 490.893s -> 487.782s (-0.63%) |
|
@rustbot ready |
| let idx = self.hygiene_ctxt.borrow_mut().get_syntax_ctxt_encoding_index(syntax_context); | ||
| idx.encode(self); | ||
| self.hygiene_ctxt.borrow_mut().enqueue_syntax_context_for_encoding(syntax_context); | ||
| self.emit_u32(self.syntax_context_remapping.map_id(syntax_context).into()); |
There was a problem hiding this comment.
| self.emit_u32(self.syntax_context_remapping.map_id(syntax_context).into()); | |
| self.emit_u32(self.syntax_context_remapping.map_id(syntax_context).as_u32()); |
It's usually better not to use into outside of generic contexts.
(Same in a few other places.)
There was a problem hiding this comment.
Turns out SyntaxContext has (almost) all methods of rustc_index::newtype_index! but it is not an rustc_index::newtype_index!, maybe we should rework it through rustc_index::newtype_index!?
There was a problem hiding this comment.
Turns out
SyntaxContexthas (almost) all methods ofrustc_index::newtype_index!but it is not anrustc_index::newtype_index!, maybe we should rework it throughrustc_index::newtype_index!?
Yes, it would be good to try (not in this PR), maybe it was just missed when similar newtypes were migrated to newtype_index!.
|
Some style nits and one remaining bigger problem (#163668 (comment)). |
|
Reminder, once the PR becomes ready for a review, use |
|
@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.
…remapping, r=<try> Remap syntax contexts and expansion ids for det. metadata encoding
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (16bad69): comparison URL. Overall result: ❌✅ regressions and improvements - please read:Benchmarking 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. Next, please: If you can, justify the regressions found in this try perf run in writing along with @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 (primary 0.4%, secondary 2.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.5%, secondary -3.4%)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: 490.736s -> 490.318s (-0.09%) |
|
@rustbot ready |
View all comments
#163495 which parallelizes AST -> HIR lowering breaks det. encoding of syntax contexts and expansions, however this PR with #162809 should fix the problem.
Now draft for perf and CI (dont look at the code). Remapping of those entities can cost us much, because unlike def ids there may be many expansions and contexts after we committed end of determinism.
r? @petrochenkov