From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by sourceware.org (Postfix) with ESMTP id 221263854800 for ; Mon, 23 Nov 2020 20:56:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 221263854800 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=kernel.crashing.org Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=segher@kernel.crashing.org Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 0ANKtbCj023944; Mon, 23 Nov 2020 14:55:37 -0600 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 0ANKtaSR023939; Mon, 23 Nov 2020 14:55:36 -0600 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Mon, 23 Nov 2020 14:55:36 -0600 From: Segher Boessenkool To: Michael Meissner , gcc-patches@gcc.gnu.org, David Edelsohn , Bill Schmidt , Peter Bergner Subject: Re: [PATCH 2/3] PowerPC: require IBM long double for pr70117. Message-ID: <20201123205536.GM2672@gate.crashing.org> References: <20201121052230.GA15702@ibm-toto.the-meissners.org> <20201121053710.GD17995@ibm-toto.the-meissners.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201121053710.GD17995@ibm-toto.the-meissners.org> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, TXREP, T_SPF_HELO_PERMERROR, T_SPF_PERMERROR autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2020 20:56:39 -0000 Hi! On Sat, Nov 21, 2020 at 12:37:10AM -0500, Michael Meissner wrote: > Since the test is explicitly checking for IBM extended double, do not try to > run it when long double is IEEE 128-bit. Before your change, it would explicitly use __ibm128 if that is not the same as long double. You need a better explanation / justification for the patch. What goes wrong without the patch? Is that to be expected? Etc. You get less coverage than before after this patch (it will now only run on systems that have double-double as long double). Segher