diff options
| author | Amy Kwan <amy.kwan1@ibm.com> | 2021-07-19 11:20:09 -0500 |
|---|---|---|
| committer | Amy Kwan <amy.kwan1@ibm.com> | 2021-07-19 11:20:21 -0500 |
| commit | 356300a3510c48f1f446cbdf580294b577435589 (patch) | |
| tree | 680b795fdd424e630d867dcd8029216917988342 /clang/lib/Frontend/InterfaceStubFunctionsConsumer.cpp | |
| parent | 8c598b77a038c87c1a0e60ce1b3c5e0961c30eda (diff) | |
| download | llvm-356300a3510c48f1f446cbdf580294b577435589.zip llvm-356300a3510c48f1f446cbdf580294b577435589.tar.gz llvm-356300a3510c48f1f446cbdf580294b577435589.tar.bz2 | |
[NFC][PowerPC] Update builtins-ppc-altivec.c to be run under `-faltivec-src-compat=mixed`
This patch adds the `-faltivec-src-compat=mixed` option to the
`builtins-ppc-altivec.c` test.
Currently, the default for `-faltivec-src-compat` is `mixed`. The reason we
explicitly specify `mixed` to the RUN lines of this test is because eventually,
the default will set to `xl`.
Having the default as `xl` changes the CHECKs of this test slightly, as it
reorders some of the `vector bool` and `vector pixel` CHECKs (since under the
`xl` option, `vector bool` and `vector pixel` are treated in the same way as
other vector scalars). Explicitly specifying `mixed` ensures that we are testing
pre-existing Clang behaviour.
Differential Revision: https://reviews.llvm.org/D106282
Diffstat (limited to 'clang/lib/Frontend/InterfaceStubFunctionsConsumer.cpp')
0 files changed, 0 insertions, 0 deletions