On 4/1/22 3:50 PM, will schmidt wrote: > Is there a testcase, new or existing, that illustrates this error path?
Well, the already existsing test case pr101849.c is where the issue was seen, but only when compiled by hand outside of the test harness and using only the -maltivec option and not the -mcpu=power10 that the test case uses. That said, I agree, pr101849.c should probably be copied into another test case file (pr103353.c) that uses options that trigger the issue so we can be sure the fix won't regress. Peter