[llvm-branch-commits] [Support] Use block numbers for LoopInfo BBMap (PR #103400)

2024-08-13 Thread Nikita Popov via llvm-branch-commits
nikic wrote: Could we have block renumbering produce a map from old to new numbers, which we can then use for straightforward analysis updates? https://github.com/llvm/llvm-project/pull/103400 ___ llvm-branch-commits mailing list llvm-branch-commits@l

[llvm-branch-commits] [Support] Use block numbers for LoopInfo BBMap (PR #103400)

2024-08-13 Thread Alexis Engelke via llvm-branch-commits
aengelke wrote: [c-t-t](http://llvm-compile-time-tracker.com/compare.php?from=2db9cb5fec35a7516b0e1d123d161ace78e14be6&to=c34780d18ac411ca2363eeff1cecd08aeb1d154a&stat=instructions:u) -0.13% stage2-O3 https://github.com/llvm/llvm-project/pull/103400 _

[llvm-branch-commits] [Support] Use block numbers for LoopInfo BBMap (PR #103400)

2024-08-13 Thread via llvm-branch-commits
llvmbot wrote: @llvm/pr-subscribers-backend-aarch64 @llvm/pr-subscribers-llvm-support Author: Alexis Engelke (aengelke) Changes Replace the DenseMap from blocks to their innermost loop a vector indexed by block numbers, when possible. This requires updating the loop info when blocks are r

[llvm-branch-commits] [Support] Use block numbers for LoopInfo BBMap (PR #103400)

2024-08-13 Thread Alexis Engelke via llvm-branch-commits
https://github.com/aengelke created https://github.com/llvm/llvm-project/pull/103400 Replace the DenseMap from blocks to their innermost loop a vector indexed by block numbers, when possible. This requires updating the loop info when blocks are renumbered. This update is currently implemented b