> Use default cost model scheduling on these test cases. All these tests > introduce scan dump failures with -mtune generic-ooo. Since the vector > cost models are the same across all three tunes, some of the tests > in PR113249 will be fixed with this patch series.
This is OK, thanks. > 39 additional unique testsuite failures (scan dumps) will still be present. > I don't know how optimal the new output is compared to the old. Should I > update > the testcase expected output to match the new scan dumps? Currently, without vector op latency, the output should come close to what's normally considered "good" (i.e. minimal number of vsetvls and so on). Therefore I'd suggest not to change the scan dumps to much except when there is a real problem. If you have a specific example that you're unsure about we can discuss this on or off list. Regards Robin
