From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: gcc-patches@gcc.gnu.org
Cc: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Subject: [PATCH] PR 79356: Do not xfail attr-alloc_size-11.c on some targets.
Date: Wed, 15 Feb 2017 17:03:00 -0000 [thread overview]
Message-ID: <20170215170154.GA4895@linux.vnet.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
The attached patch removes the xfail on two sub tests of
attr-alloc_size-11.c for the targets who were reported to produce
an XPASS:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79356
Tested on s390x biarch and s390. Please check if the strings for
the other targets are correct.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
[-- Attachment #2: 0001-ChangeLog --]
[-- Type: text/plain, Size: 137 bytes --]
gcc/testsuite/ChangeLog-pr79356
PR 79356
* gcc.dg/attr-alloc_size-11.c: Remove xfail for aarch64, ia64*,
powerpc*, sparc* and s390*.
[-- Attachment #3: 0001-PR-79356-Do-not-xfail-attr-alloc_size-11.c-on-some-t.patch --]
[-- Type: text/plain, Size: 2030 bytes --]
From 8486df212e3284e5fbdfb3f47bff59652e1e55a7 Mon Sep 17 00:00:00 2001
From: Dominik Vogt <vogt@linux.vnet.ibm.com>
Date: Wed, 15 Feb 2017 17:39:07 +0100
Subject: [PATCH] PR 79356: Do not xfail attr-alloc_size-11.c on some
targets.
---
gcc/testsuite/gcc.dg/attr-alloc_size-11.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/gcc/testsuite/gcc.dg/attr-alloc_size-11.c b/gcc/testsuite/gcc.dg/attr-alloc_size-11.c
index fac8b18..077b725 100644
--- a/gcc/testsuite/gcc.dg/attr-alloc_size-11.c
+++ b/gcc/testsuite/gcc.dg/attr-alloc_size-11.c
@@ -45,9 +45,10 @@ typedef __SIZE_TYPE__ size_t;
return CAT (alloc_anti_range_, __LINE__)(n); \
} typedef void dummy /* Require a semicolon. */
-/* The following tests fail because of missing range information. */
-TEST (signed char, SCHAR_MIN + 2, ALLOC_MAX); /* { dg-warning "argument 1 range \\\[13, \[0-9\]+\\\] exceeds maximum object size 12" "missing range info for signed char" { xfail *-*-* } } */
-TEST (short, SHRT_MIN + 2, ALLOC_MAX); /* { dg-warning "argument 1 range \\\[13, \[0-9\]+\\\] exceeds maximum object size 12" "missing range info for short" { xfail *-*-* } } */
+/* The following tests fail on some targets because of missing range
+ information. */
+TEST (signed char, SCHAR_MIN + 2, ALLOC_MAX); /* { dg-warning "argument 1 range \\\[13, \[0-9\]+\\\] exceeds maximum object size 12" "missing range info for signed char" { xfail { ! "aarch64-*-* ia64*-*-* powerpc*-*-* s390*-*-* sparc*-*-*" } } } */
+TEST (short, SHRT_MIN + 2, ALLOC_MAX); /* { dg-warning "argument 1 range \\\[13, \[0-9\]+\\\] exceeds maximum object size 12" "missing range info for short" { xfail { ! "aarch64-*-* ia64*-*-* powerpc*-*-* s390*-*-* sparc*-*-*" } } } */
TEST (int, INT_MIN + 2, ALLOC_MAX); /* { dg-warning "argument 1 range \\\[13, \[0-9\]+\\\] exceeds maximum object size 12" } */
TEST (int, -3, ALLOC_MAX); /* { dg-warning "argument 1 range \\\[13, \[0-9\]+\\\] exceeds maximum object size 12" } */
--
2.3.0
next reply other threads:[~2017-02-15 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 17:03 Dominik Vogt [this message]
2017-02-16 10:45 ` Rainer Orth
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=20170215170154.GA4895@linux.vnet.ibm.com \
--to=vogt@linux.vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=krebbel@linux.vnet.ibm.com \
/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).