aboutsummaryrefslogtreecommitdiff
path: root/gcc/value-range.cc
diff options
context:
space:
mode:
authorRichard Sandiford <richard.sandiford@arm.com>2022-10-20 10:37:33 +0100
committerRichard Sandiford <richard.sandiford@arm.com>2022-10-20 10:37:33 +0100
commit57675c7f92a3bd3ca8dae1faac7f2f51d40e0f9e (patch)
tree4d3cda0f39a73292bc96f0071693a4a2eb758b3d /gcc/value-range.cc
parent6bec66640597e2604f51fc1642c7d279164cd442 (diff)
downloadgcc-57675c7f92a3bd3ca8dae1faac7f2f51d40e0f9e.zip
gcc-57675c7f92a3bd3ca8dae1faac7f2f51d40e0f9e.tar.gz
gcc-57675c7f92a3bd3ca8dae1faac7f2f51d40e0f9e.tar.bz2
aarch64: Prevent generation of /M BRKAS and BRKBS
Bit of a brown-paper-bag bug, but: GCC was generating non-existent merging forms of BRKAS and BRKBS. Those instructions only support zero predication (although BRKA and BRKB support both). gcc/ * config/aarch64/aarch64-sve.md (*aarch64_brk<brk_op>_cc): Remove merging alternative. (*aarch64_brk<brk_op>_ptest): Likewise. gcc/testsuite/ * gcc.target/aarch64/sve/acle/general/brka_1.c: Expect a separate PTEST instruction. * gcc.target/aarch64/sve/acle/general/brkb_1.c: Likewise.
Diffstat (limited to 'gcc/value-range.cc')
0 files changed, 0 insertions, 0 deletions