https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102997
--- Comment #9 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- (In reply to Martin Liška from comment #8) > Started with Aldy's commit > r12-4526-gd8edfadfc7a9795b65177a50ce44fd348858e844. Hmmm, this commit disables problematic threads we've agreed are detrimental to loop form. So it's not something the threader did, but something it's not allowed to do. This PR may need a loop expert to analyze. I guess, technically it could be something we could catch past the loop optimizers, but that's usually rarer.
