aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHans-Peter Nilsson <hp@axis.com>2023-02-24 17:22:02 +0100
committerHans-Peter Nilsson <hp@bitrange.com>2023-02-28 02:04:20 +0100
commit8c58f4b798177d419c5af37b7e23c490849f2d45 (patch)
tree7931668e03cd4c421fa4dd6e37ad4a8c29ba19f9
parentbf0e0fc0ea47698c81ddb0eb00a71f9ad251c4a1 (diff)
downloadgcc-8c58f4b798177d419c5af37b7e23c490849f2d45.zip
gcc-8c58f4b798177d419c5af37b7e23c490849f2d45.tar.gz
gcc-8c58f4b798177d419c5af37b7e23c490849f2d45.tar.bz2
testsuite: Add -fno-ivopts to gcc.dg/Wuse-after-free-2.c, PR108828
For cris-elf before this patch, ever since it was added, this test gets: Running /x/gcc/testsuite/gcc.dg/dg.exp ... FAIL: gcc.dg/Wuse-after-free-2.c (test for warnings, line 115) FAIL: gcc.dg/Wuse-after-free-2.c (test for warnings, line 116) and comparing tree dumps with a native x86_64-pc-linux-gnu run shows a suspicious difference in the "180t.ivopts" dump. Indeed -fno-ivopts makes the warning appear for cris-elf too. It was suggested to simply add -fno-ivopts to the test-flags, like before -fno-tree-loop-distribute-patterns was added; thus. PR tree-optimization/108828 * gcc.dg/Wuse-after-free-2.c: Add -fno-ivopts.
-rw-r--r--gcc/testsuite/gcc.dg/Wuse-after-free-2.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/gcc/testsuite/gcc.dg/Wuse-after-free-2.c b/gcc/testsuite/gcc.dg/Wuse-after-free-2.c
index 68ec758..ebc0516 100644
--- a/gcc/testsuite/gcc.dg/Wuse-after-free-2.c
+++ b/gcc/testsuite/gcc.dg/Wuse-after-free-2.c
@@ -1,6 +1,6 @@
/* PR middle-end/104232 - spurious -Wuse-after-free after conditional free
{ dg-do compile }
- { dg-options "-O2 -Wall -fno-tree-loop-distribute-patterns" } */
+ { dg-options "-O2 -Wall -fno-tree-loop-distribute-patterns -fno-ivopts" } */
void free (void*);
@@ -108,7 +108,8 @@ int warn_cond_loop (char *p)
char *q = p;
/* -fno-tree-loop-distribute-patterns ensures this does not get converted
- into rawmemchr (making q and p unrelated). */
+ into rawmemchr (making q and p unrelated). Also, -fno-ivopts is required
+ for some targets, to not lose track of the pointer. */
while (*q)
++q;