https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118055
--- Comment #3 from Hongtao Liu <liuhongt at gcc dot gnu.org> --- > > Is it perhaps that the test is brittle; mostly target-specific despite being > at the tree-level and that instead the scan-test should be a specific > known-matching target list? The testcase is used to detect load/store motion optimization which relies on loop unrolling, my commit adjusted unroll heuritic to prevent some "bad"(performance) unroll and breaks the testcase on some targets. For this testcase itself, (for some targets) it may be necessary to add --param max-completely-peeled-insns=300 to ensure that unroll occurs. For performance perpective, the targets may need to Fine-tuning the parameter of max-completely-peeled-insns according to benchmarks.
