https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113249
--- Comment #4 from Robin Dapp <rdapp at gcc dot gnu.org> --- > One of the reasons I've been testing things with generic-ooo is because > generic-ooo had initial vector pipelines defined. For cleaning up the > scheduler, I copied over the generic-ooo pipelines into generic and sifive-7 > md files. As you mentioned, the scan dump fails are likely less optimal code > sequences for the as a result of the cost model. I'm planning on sending up > a patch in my series that adds -fno-schedule-insns -fno-schedule-insns2 to > the dump scan tests that fail but do you think it would be better to hard > code the tune instead? It's a bit difficult to say, actually both is not ideal but there is no ideal way anyway :) Disabling scheduling is probably fine for all the intrinsics tests because it can be argued that the expected output is very close to the input anyway. For others it might depend on the intention of the test. But, in order to get them out of the way, I think it should be ok to just disabling scheduling and take care of the intention of the test later.
