https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80925
--- Comment #11 from Bill Schmidt <wschmidt at gcc dot gnu.org> --- Well, I should be more careful -- the behavior you see is probably reasonable for these runtime tests, since the testing infrastructure isn't aware that you built for an older architecture on the POWER8 it will be running on. And I think we still have an undiagnosed problem. We are seeing these tests fail natively on POWER6 and POWER7 systems where we have buildbots sending results to gcc-testresults. In that scenario, the override you discovered presumably wouldn't kick in. Bill Seurer, can you run one of these tests by hand on the regtester machines, and save the output from -fdump-tree-vect-details? Hopefully that will give me some insight into why the tests still fail there when they should use the expensive cost modeling.
