https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
--- Comment #12 from Ilya Leoshkevich <iii at linux dot ibm.com> --- > Well, it apparently has found new jump threading opportunities after > partition_blocks. Are such changes useful? Does it happen often? It's still combine that was responsible for this particular opportunity. I've added a simple counter of threaded edges and built two compiler versions: with and without the patch from comment 3. The value of the counter is the same in both cases for the code from this bugreport. Furthermore, I've built SPEC 2006 and SPEC 2017 with vanilla and patched compilers and aggregated the counter values. When doing jump threading right after reload, 3889 edges are threaded. When doing jump threading right after combine, 3918 edges are threaded. Both figures are more or less the same, we even end up losing some opportunities if we delay jump threading.
