EffectiveVisibility: split fixed-point iteration into 2 stages#156138
EffectiveVisibility: split fixed-point iteration into 2 stages#156138Bryanskiy wants to merge 2 commits intorust-lang:mainfrom
EffectiveVisibility: split fixed-point iteration into 2 stages#156138Conversation
|
@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.
`EffectiveVisibility`: split fixed-point iteration into 2 stages
This comment has been minimized.
This comment has been minimized.
fad9377 to
d76cb84
Compare
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (0f6b3e5): 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 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 1.7%, secondary 1.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.7%, 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: 495.891s -> 494.917s (-0.20%) |
|
@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.
`EffectiveVisibility`: split fixed-point iteration into 2 stages
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (7ee0eba): 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 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.1%, secondary 1.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -2.1%, secondary -0.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: 495.518s -> 493.52s (-0.40%) |
Use fixed-point iteration exclusively for modules and use chains during
EffectiveVisibilitycomputation. Other defs/fields are computed in a separate single pass.r? @petrochenkov