aboutsummaryrefslogtreecommitdiff
path: root/gcc/config/i386/sse.md
diff options
context:
space:
mode:
authorAldy Hernandez <aldyh@redhat.com>2021-10-23 08:59:24 +0200
committerAldy Hernandez <aldyh@redhat.com>2021-10-26 08:20:11 +0200
commit4e417eea8f3f14131f7370f9bd5dd568611d11df (patch)
tree2b57fd1fdd30de8f04ab9cc7c3d88efca3d76574 /gcc/config/i386/sse.md
parente53fbb17839723ea1697fcbaf76b1c092675eaaf (diff)
downloadgcc-4e417eea8f3f14131f7370f9bd5dd568611d11df.zip
gcc-4e417eea8f3f14131f7370f9bd5dd568611d11df.tar.gz
gcc-4e417eea8f3f14131f7370f9bd5dd568611d11df.tar.bz2
[PR testsuite/102857] Tweak ssa-dom-thread-7.c for aarch64.
First, ssa-dom-thread-7 was looking at a dump file that was not being generated. This probably happened in the detangling of the VRP threader from VRP, and I didn't notice because the test came back as with UNRESOLVED instead of FAIL. Second, aarch64 gets far more threads than other architectures (20 versus 12). The difference is sufficiently different to make the regex awkward. We already have special casing for aarch64 in other parts of this test, so perhaps it's simplest to have an arch specific test for the thread3 count. I don't know perhaps there's a better way. I wake up with chills in the middle of the night thinking about this test ;-). Tested on x86-64 Linux and aarch64 Linux. gcc/testsuite/ChangeLog: PR testsuite/102857 * gcc.dg/tree-ssa/ssa-dom-thread-7.c: Add -fdump-tree-vrp2-stats. Tweak for aarch64.
Diffstat (limited to 'gcc/config/i386/sse.md')
0 files changed, 0 insertions, 0 deletions