aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYunQiang Su <syq@gcc.gnu.org>2024-06-08 16:05:13 +0800
committerYunQiang Su <syq@gcc.gnu.org>2024-06-10 14:42:42 +0800
commit8e2eb6039d183b7c571da9eb83b933021c5b29be (patch)
treeb2ca85eb4ae039e995ac63d50171e5669d239938
parentc1429e3a8da0cdfe9391e1e9b2c7228d896a3a87 (diff)
downloadgcc-8e2eb6039d183b7c571da9eb83b933021c5b29be.zip
gcc-8e2eb6039d183b7c571da9eb83b933021c5b29be.tar.gz
gcc-8e2eb6039d183b7c571da9eb83b933021c5b29be.tar.bz2
MIPS/testsuite: add -mno-branch-likely to r10k-cache-barrier-13.c
In mips.cc(mips_reorg_process_insns), there is this claim: Also delete cache barriers if the last instruction was an annulled branch. INSN will not be speculatively executed. And with -O1 on mips64, we can generate binary code like this, which fails this test. gcc/testsuite * gcc.target/mips/r10k-cache-barrier-13.c: Add -mno-branch-likely option.
-rw-r--r--gcc/testsuite/gcc.target/mips/r10k-cache-barrier-13.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/testsuite/gcc.target/mips/r10k-cache-barrier-13.c b/gcc/testsuite/gcc.target/mips/r10k-cache-barrier-13.c
index ee9c84b..ac005fb 100644
--- a/gcc/testsuite/gcc.target/mips/r10k-cache-barrier-13.c
+++ b/gcc/testsuite/gcc.target/mips/r10k-cache-barrier-13.c
@@ -1,4 +1,4 @@
-/* { dg-options "-mr10k-cache-barrier=store" } */
+/* { dg-options "-mr10k-cache-barrier=store -mno-branch-likely" } */
/* Test that indirect calls are protected. */