From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-375709-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 24619 invoked by alias); 3 Dec 2011 21:09:10 -0000
Received: (qmail 24609 invoked by uid 22791); 3 Dec 2011 21:09:09 -0000
X-SWARE-Spam-Status: No, hits=-2.8 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00,TW_IB
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 03 Dec 2011 21:08:56 +0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/51057] FAIL: gfortran.dg/quad_2.f90  -O0  execution test on powerpc*-*-*
Date: Sat, 03 Dec 2011 21:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51057-4-5UHkEeEsHF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51057-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51057-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-12/txt/msg00275.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51057

--- Comment #4 from Iain Sandoe <iains at gcc dot gnu.org> 2011-12-03 21:08:26 UTC ---
(In reply to comment #3)
> On Sat, Dec 03, 2011 at 08:36:43PM +0000, iains at gcc dot gnu.org wrote:

> This test came into being when libquadmath came into the tree.
> The correct, and only, solution for targets whose long double
> representation is double-double math is to XFAIL the test on those
> targets.

Elsewhere in the test suite, if a test is meaningless or impossible to complete
in the absence of a capability - the test is made conditional on that
capability, rather than having a long list of XFAILs.

If this is really not possible here, then I'll prepare an XFAIL patch, but it's
not an ideal solution.