[EXPERIMENT] Run jump threading to fixpoint#156873
Conversation
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[EXPERIMENT] Run jump threading to fixpoint
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (d89dc81): 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 1.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -0.2%, secondary 0.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 509.286s -> 510.466s (0.23%) |
c18c896 to
4438f2a
Compare
|
The job Click to see the possible cause of the failure (guessed by this bot) |

JumpThreading implementation can fully unfold a DFA.
TODO: Before enabling such feature, we need to ensure that we do not create irreducible control flow for LLVM to choke on.