https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120805
--- Comment #12 from Avinash Jayakar <avinashd at linux dot ibm.com> --- (In reply to Segher Boessenkool from comment #10) > As a meta-comment: almost everything using scan-assembler-times is > obfuscated. > > It should always say in comments *why* it expects it as many times as that, > so that when the test starts failing it is somewhat clear what happened :-) I had a hard time understanding what the test case does for these vector test case. It looks like it just checks whether the load and store instructions are generated in the epilogue for each line in the loop. Ideally since there are 7 additions and 10 types, there should be a load vector and store vector instruction for each addition roughly. But the test looks for 120 lxv/lxvx instruction which also sees the instruction in the main loop as well as some loads happening from TOC, and is very confusing to figure out what the check is doing. Would it be better to just check what is generated in the epilogue instead of seeing the main loop as well for these tests?
