From: Hans-Peter Nilsson <hp@axis.com>
To: <gcc-patches@gcc.gnu.org>
Subject: [PATCH] testsuite: XFAIL g++.dg/pr71488.C and warn/Warray-bounds-16.C, PR107561
Date: Thu, 2 Feb 2023 22:01:39 +0100 [thread overview]
Message-ID: <20230202210139.E1AF420426@pchp3.se.axis.com> (raw)
Tested cris-elf, native x86_64-pc-linux-gnu.
Ok to commit?
--- 8< ---
These appear as regressions from a baseline before
r13-3761-ga239a63f868e29. See the PR trail.
Note that the warning for g++.dg/pr71488.C is for a *header*
file, thus we can't match the line number (sanely).
gcc/testsuite:
PR tree-optimization/107561
* g++.dg/warn/Warray-bounds-16.C: XFAIL bogus "overflows destination"
warning.
* g++.dg/pr71488.C: Ditto, but just for ilp32 targets.
---
gcc/testsuite/g++.dg/pr71488.C | 1 +
gcc/testsuite/g++.dg/warn/Warray-bounds-16.C | 1 +
2 files changed, 2 insertions(+)
diff --git a/gcc/testsuite/g++.dg/pr71488.C b/gcc/testsuite/g++.dg/pr71488.C
index ffe30f1afeb1..a89e6465a945 100644
--- a/gcc/testsuite/g++.dg/pr71488.C
+++ b/gcc/testsuite/g++.dg/pr71488.C
@@ -3,6 +3,7 @@
// { dg-options "-O3 -std=c++11" }
// { dg-additional-options "-msse4" { target sse4_runtime } }
// { dg-require-effective-target c++11 }
+// { dg-bogus "size 0 overflows" "pr107561" { xfail *-*-* } 0 }
#include <valarray>
diff --git a/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C b/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C
index 89cbadb91c7b..49d3437fa1b7 100644
--- a/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C
+++ b/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C
@@ -20,6 +20,7 @@ struct S
for (int i = 0; i < m; i++)
new (p + i) int (); /* { dg-bogus "bounds" "pr102690" { xfail *-*-* } } */
+ // { dg-bogus "size 0 overflows" "pr107561" { xfail ilp32 } .-1 }
}
};
--
2.30.2
reply other threads:[~2023-02-02 21:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230202210139.E1AF420426@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).