As described in the PR, gcc.dg/attr-alloc_size-4.c was FAILing on 32-bit
x86 targets. Fixed as follows by removing the mismatch between #if
conditions and target selectors.
Tested with the appropriate runtest invocations on i386-pc-solaris2.12
and amd64-pc-solaris2.12, installed on mainline.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
2017-01-19 Rainer Orth <r...@cebitec.uni-bielefeld.de>
PR testsuite/79051
* gcc.dg/attr-alloc_size-4.c (test_int_range) [__i386__ ||
__x86_64__]: Allow for target i?86-*-*.
# HG changeset patch
# Parent a83e32258f0450b5c0538ef71d8c6230eb72180f
Further fix for PR testsuite/79051
diff --git a/gcc/testsuite/gcc.dg/attr-alloc_size-4.c b/gcc/testsuite/gcc.dg/attr-alloc_size-4.c
--- a/gcc/testsuite/gcc.dg/attr-alloc_size-4.c
+++ b/gcc/testsuite/gcc.dg/attr-alloc_size-4.c
@@ -140,7 +140,7 @@ test_int_range (int n)
#if __i386__ || __x86_64__
/* Avoid failures described in bug 79051. */
- sink (f_int_1 (SAR (min + 2, 1235))); /* { dg-warning "argument 1 range \\\[1236, \[0-9\]+\\\] exceeds maximum object size 1234" "" { target { x86_64-*-* } } } */
+ sink (f_int_1 (SAR (min + 2, 1235))); /* { dg-warning "argument 1 range \\\[1236, \[0-9\]+\\\] exceeds maximum object size 1234" "" { target { i?86-*-* x86_64-*-* } } } */
#endif
sink (f_int_1 (SAR (0, max))); /* { dg-warning "argument 1 range \\\[-\[0-9\]*, -1\\\] is negative" } */
