Between 20181022 (r265393) and 20181023 (r265430), gcc.dg/pr78973-2.c
began to XPASS on a large number of targets:

+XPASS: gcc.dg/pr78973-2.c ilp32 (test for warnings, line 16)

The following patch fixes this by removing the xfail on dg-warning.
Tested on i386-pc-solaris2.11, sparc-sun-solaris2.11, and
x86_64-pc-linux-gnu (both multilibs in every case).  I'd usually just
install the patch as obvious, but am holding back since none of the
patches in that range obviously caused that.

        Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University


2018-10-24  Rainer Orth  <r...@cebitec.uni-bielefeld.de>

        * gcc.dg/pr78973-2.c: Remove xfail on dg-warning.

# HG changeset patch
# Parent  c704e85a30095c986599b2a7af488d213703bd44
Don't xfail gcc.dg/pr78973-2.c on non-ilp64 targets

diff --git a/gcc/testsuite/gcc.dg/pr78973-2.c b/gcc/testsuite/gcc.dg/pr78973-2.c
--- a/gcc/testsuite/gcc.dg/pr78973-2.c
+++ b/gcc/testsuite/gcc.dg/pr78973-2.c
@@ -14,7 +14,7 @@ void f (int n)
 {
   if (n <= 4)
     p = __builtin_malloc (n);
-  /* { dg-warning "argument 1 range \\\[\[0-9\]+, \[0-9\]+\\\] exceeds maximum object size 4" "ilp32" { xfail { ! lp64 } } .-1 } */
+  /* { dg-warning "argument 1 range \\\[\[0-9\]+, \[0-9\]+\\\] exceeds maximum object size 4" "ilp32" { target *-*-* } .-1 } */
 }
 
 void g (unsigned n)

Reply via email to