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 00D76385842B; Thu, 28 Apr 2022 16:08:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 00D76385842B Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=kernel.crashing.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=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 23SG6hnO012356; Thu, 28 Apr 2022 11:06:43 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 23SG6gu5012354; Thu, 28 Apr 2022 11:06:42 -0500 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Thu, 28 Apr 2022 11:06:42 -0500 From: Segher Boessenkool To: Matthias Kretz Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org, David Edelsohn , Alexandre Oliva Subject: Re: [PATCH] libstdc++: ppc: conditionalize vsx-only simd intrinsics Message-ID: <20220428160642.GT25951@gate.crashing.org> References: <15649943.RDIVbhacDa@minbar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15649943.RDIVbhacDa@minbar> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libstdc++@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++ mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2022 16:08:49 -0000 On Thu, Apr 28, 2022 at 03:56:18PM +0200, Matthias Kretz wrote: > On Thursday, 28 April 2022 08:09:54 CEST Alexandre Oliva via Gcc-patches > wrote: > > libstdc++'s bits/simd.h section for PPC (Altivec) defines various > > intrinsic vector types that are only available along with VSX: 64-bit > > long double, double, (un)signed long long, and 64-bit (un)signed long. > > Oh, so uttering `__vector double` is ill-formed (now) without VSX? I'm fairly > certain I tested without VSX and the __intrinsic_type_impl definitions were > fine. It always was undefined (and did not work): error: use of 'double' in AltiVec types is invalid without '-mvsx' Segher