https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #9 from Martin Sebor <msebor at gcc dot gnu.org> --- It might be possible for some. I'm not sure how successful it would be for others. The thread_jumps pass runs four times and moving the warn_restrict pass before its first instance results in dozens of regressions. This particular instance of the warning goes away if the warn_restrict pass is moved before the second to last threads_jump pass, but that still causes regressions. Moving the pass just before the last threads_jump pass doesn't help.