resolve/effective-visibility: Stop recalculating current normal module#103688
resolve/effective-visibility: Stop recalculating current normal module#103688petrochenkov wants to merge 1 commit intorust-lang:masterfrom
Conversation
|
r? @wesleywiser (rustbot has picked a reviewer for you, use r? to override) |
|
@bors try @rust-timer queue |
|
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
|
⌛ Trying commit 207c68156a2207984777602b5f8822cf598935ba with merge 05d876bca703933abce2c6894c4d51cbb59b7756... |
|
☀️ Try build successful - checks-actions |
|
Queued 05d876bca703933abce2c6894c4d51cbb59b7756 with parent a9ef100, future comparison URL. |
|
Finished benchmarking commit (05d876bca703933abce2c6894c4d51cbb59b7756): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
It becomes relatively expensive if done often and shows up during perf profiling Also drop `extern` blocks from the effective visibility table, they are nominally private and it doesn't make sense to keep them there.
207c681 to
39888c4
Compare
|
☔ The latest upstream changes (presumably #103841) made this pull request unmergeable. Please resolve the merge conflicts. |
|
Blocked on #103965. |
|
This change was applied to #104602, closing. |
It becomes relatively expensive if done often and shows up during perf profiling
Also drop
externblocks from the effective visibility table, they are nominally private and it doesn't make sense to keep them there.cc @Bryanskiy