From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-451256-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 27216 invoked by alias); 7 Apr 2017 08:45:41 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 27048 invoked by uid 89); 7 Apr 2017 08:45:40 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-11.9 required=5.0 tests=BAYES_00,GIT_PATCH_2,GIT_PATCH_3,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=
X-HELO: mx2.suse.de
Received: from mx2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 07 Apr 2017 08:45:38 +0000
Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254])	by mx2.suse.de (Postfix) with ESMTP id 5BFD3ACC6;	Fri,  7 Apr 2017 08:45:37 +0000 (UTC)
Date: Fri, 07 Apr 2017 08:45:00 -0000
From: Richard Biener <rguenther@suse.de>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix PR80334
In-Reply-To: <yddpogotxsz.fsf@CeBiTec.Uni-Bielefeld.DE>
Message-ID: <alpine.LSU.2.20.1704071045230.30715@zhemvz.fhfr.qr>
References: <alpine.LSU.2.20.1704061438350.30715@zhemvz.fhfr.qr> <ydda87tuuyn.fsf@CeBiTec.Uni-Bielefeld.DE> <alpine.LSU.2.20.1704070848140.30715@zhemvz.fhfr.qr> <yddtw60tyq5.fsf@CeBiTec.Uni-Bielefeld.DE> <alpine.LSU.2.20.1704071032300.30715@zhemvz.fhfr.qr> <yddpogotxsz.fsf@CeBiTec.Uni-Bielefeld.DE>
User-Agent: Alpine 2.20 (LSU 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-SW-Source: 2017-04/txt/msg00355.txt.bz2

On Fri, 7 Apr 2017, Rainer Orth wrote:

> Hi Richard,
> 
> >> > Any suggestion how to mitigate that?  Possible solution includes
> >> > adding { target { ! ... } } to dg-do run.
> >> 
> >> No idea.  However, according to gcc-testresults there are other
> >> failures: s390-ibm-inux-gnu and s390x-ibm-linux-gnu so far.
> >> 
> >> This might argue against just excluding a random list of failing targets.
> >
> > Hmm.  Does using __BIGGEST_ALIGNMENT__, thus
> >
> > int
> > main()
> > {
> >   alignas(__BIGGEST_ALIGNMENT__) B b[3];
> > ...
> >
> > work for you?
> 
> it does: the test now PASSes on sparc-sun-solaris2.12 and continues to
> do so in i386-pc-solaris2.12, both 32 and 64-bit.

Tested on x86_64-unknwon-linux-gnu, applied.

Richard.

2017-04-07  Richard Biener  <rguenther@suse.de>

	PR tree-optimization/80334
	* g++.dg/torture/pr80334.C: Use __BIGGEST_ALIGNMENT__ for
	alignas on stack.

Index: gcc/testsuite/g++.dg/torture/pr80334.C
===================================================================
--- gcc/testsuite/g++.dg/torture/pr80334.C	(revision 246752)
+++ gcc/testsuite/g++.dg/torture/pr80334.C	(working copy)
@@ -8,7 +8,7 @@ char x;
 int
 main()
 {
-  alignas(16) B b[3];
+  alignas(__BIGGEST_ALIGNMENT__) B b[3];
   for (int i = 0; i < 3; i++) b[i].unpacked.c = 'a' + i;
   for (int i = 0; i < 3; i++)
     {