The test xfailed for ILP32 has been apparently passing for some time.
I've removed the xfail after confirming in with -m32 on x86_64 and
powerpc64.
Martin
commit 68b938fada4c728c0b850b44125d9a173c01c8fb
Author: Martin Sebor <mse...@redhat.com>
Date: Thu Jul 8 16:22:25 2021 -0600
testsuite: Remove an xfail.
gcc/testsuite/ChangeLog:
* gcc.dg/Wstringop-overflow-43.c: Remove an xfail.
diff --git a/gcc/testsuite/gcc.dg/Wstringop-overflow-43.c b/gcc/testsuite/gcc.dg/Wstringop-overflow-43.c
index 14ab925afdc..6d045c58bf6 100644
--- a/gcc/testsuite/gcc.dg/Wstringop-overflow-43.c
+++ b/gcc/testsuite/gcc.dg/Wstringop-overflow-43.c
@@ -167,9 +167,7 @@ void warn_memset_reversed_range (void)
/* The following are represented as ordinary ranges with reversed bounds
and those are handled. */
T1 (p, SAR (INT_MIN, 11), n11); // { dg-warning "writing 11 or more bytes into a region of size 0" }
- /* In ILP32 the offset in the following has no range info associated
- with it. */
- T1 (p, SAR (INT_MIN, 1), n11); // { dg-warning "writing 11 or more bytes into a region of size 0" "pr?????" { xfail ilp32 } }
+ T1 (p, SAR (INT_MIN, 1), n11); // { dg-warning "writing 11 or more bytes into a region of size 0" }
T1 (p, SAR (INT_MIN, 0), n11); // { dg-warning "writing 11 or more bytes into a region of size 0" }
/* Also represented as a true anti-range. */
T1 (p, SAR ( -12, -11), n11); // { dg-warning "writing 11 or more bytes into a region of size \\d+" }
