diff options
| author | Alan Modra <amodra@gmail.com> | 2020-10-29 17:17:47 +1030 |
|---|---|---|
| committer | Alan Modra <amodra@gmail.com> | 2020-12-06 12:32:43 +1030 |
| commit | 1fab57f26ec24ce4e5672a7515c88611eba2483f (patch) | |
| tree | 36c434b4668babda1210a0194ab7ee452fe6cf05 /gcc/tree-vectorizer.h | |
| parent | 6e1edf48ebe8881bc7c5e54157f47169290bdd12 (diff) | |
| download | gcc-1fab57f26ec24ce4e5672a7515c88611eba2483f.zip gcc-1fab57f26ec24ce4e5672a7515c88611eba2483f.tar.gz gcc-1fab57f26ec24ce4e5672a7515c88611eba2483f.tar.bz2 | |
Re: testsuite: Adjust target requirements for sad-vectorize and signbit
Fixes
FAIL: gcc.target/powerpc/signbit-1.c scan-assembler-not stxvd2x
FAIL: gcc.target/powerpc/signbit-1.c scan-assembler-times mfvsrd 3
FAIL: gcc.target/powerpc/signbit-1.c scan-assembler-times srdi 3
FAIL: gcc.target/powerpc/signbit-2.c scan-assembler-times ld 1
FAIL: gcc.target/powerpc/signbit-2.c scan-assembler-times srdi 1
on powerpc-linux (or powerpc64-linux biarch -m32).
signbit-1.c is quite obviously a 64-bit only testcase given the
scan-assembler directives, and the purpose of the testcase to verify
the 64-bit only UNSPEC_SIGNBIT patterns. It could be made to pass for
-m32 by adding -mpowerpc64, but that option that isn't very effective
when bi-arch testing and results in errors on rs6000-aix. And it is
pointless to match -m32 stores to the stack followed by loads, which
is what we do at the moment.
signbit-2.c on the other hand has more reasonable 32-bit output.
* gcc.target/powerpc/signbit-1.c: Reinstate lp64 condition.
* gcc.target/powerpc/signbit-2.c: Match 32-bit output too.
Diffstat (limited to 'gcc/tree-vectorizer.h')
0 files changed, 0 insertions, 0 deletions