on 2022/4/2 5:52 AM, Peter Bergner wrote: > 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 > >
Thanks for the comments, Will and Peter! I thought of adding one case before but gave up as the case still emits error messages which can be fragile and are not test points and I didn't find any similar test cases for similar scenarios in powerpc test suite. Your suggestions make me consider it seriously again. The patch v2 was just posted with one test case: https://gcc.gnu.org/pipermail/gcc-patches/2022-April/592916.html. Hope it looks better to you, thanks again! BR, Kewen
