Use scan-tree-dump instead of scan-tree-dump-times for some vect tests
authorRichard Sandiford <richard.sandiford@arm.com>
Wed, 6 Nov 2019 12:31:19 +0000 (12:31 +0000)
committerRichard Sandiford <rsandifo@gcc.gnu.org>
Wed, 6 Nov 2019 12:31:19 +0000 (12:31 +0000)
commitfeba3d8838118d3c41b8e25f13beaa6a15b38302
tree8a7c4f0aaa020df6adc9c7384d5e027fb8961b0f
parent8ec5b16a9a3dbd6d825596c22f1bc32646de28fe
Use scan-tree-dump instead of scan-tree-dump-times for some vect tests

With later patches, we're able to vectorise the epilogues of these tests
on AArch64 and so get two instances of "vectorizing stmts using SLP".
Although it would be possible with a bit of effort to predict when
this happens, it doesn't seem important whether we get 1 vs. 2
occurrences.  All that matters is zero vs. nonzero.

2019-11-06  Richard Sandiford  <richard.sandiford@arm.com>

gcc/testsuite/
* gcc.dg/vect/slp-9.c: Use scan-tree-dump rather than
scan-tree-dump-times.
* gcc.dg/vect/slp-widen-mult-s16.c: Likewise.
* gcc.dg/vect/slp-widen-mult-u8.c: Likewise.

From-SVN: r277881
gcc/testsuite/ChangeLog
gcc/testsuite/gcc.dg/vect/slp-9.c
gcc/testsuite/gcc.dg/vect/slp-widen-mult-s16.c
gcc/testsuite/gcc.dg/vect/slp-widen-mult-u8.c