https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54089
--- Comment #77 from Alexander Klepikov <klepikov.alex+bugs at gmail dot com> --- > It'd be good if the newly added passes are ran only with -O2 or higher. This can be confusing to users when they discover that not all invariants are moved out of loops. Then we should inform them about that at least. > Or even better, if we can find a way to enable them only when actually > needed. > E.g. when it's splitting a shift insn that will potentially need the loop > optimizations again, set a flag in the function. I'm thinking about this for some time. We know that we should potentially run additional loop optimization pass when we're splitting libcall. I did not find the way to know in what function we are splitting yet. > However, to get better test coverage, it's better first let the additional > loop passes run all the time to uncover any potential issues. Later the > above can be added as a supplementary optimization. I see some strange new exec fails only at testsuite logs. Right now I'm trying to find the cause.
