https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104067
--- Comment #6 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- (In reply to Jeffrey A. Law from comment #5) > I briefly looked at the other BZ last week, but didn't make much headway. > The first thing that stood out was why are we threading around the loop. I > thought that was disabled. Anyway, Aldy and/or I will take both of these in > the coming days. This is the threadfull2 pass which is the most aggressive of the threaders. Loop optimizations have completed, so anything goes wrt loops (as per jt_path_registry::cancel_invalid_paths). Note that the issue here is not exactly a backedge problem as in PR103721, but a domination problem. I will comment in the other PR as they are related.
