From: Segher Boessenkool <segher@kernel.crashing.org>
To: Matthias Kretz <m.kretz@gsi.de>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
David Edelsohn <dje.gcc@gmail.com>,
Alexandre Oliva <oliva@adacore.com>
Subject: Re: [PATCH] libstdc++: ppc: conditionalize vsx-only simd intrinsics
Date: Thu, 28 Apr 2022 11:06:42 -0500 [thread overview]
Message-ID: <20220428160642.GT25951@gate.crashing.org> (raw)
In-Reply-To: <15649943.RDIVbhacDa@minbar>
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
prev parent reply other threads:[~2022-04-28 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 6:09 Alexandre Oliva
2022-04-28 13:03 ` Segher Boessenkool
2022-04-29 1:53 ` Alexandre Oliva
2022-04-29 18:44 ` Matthias Kretz
2022-05-02 21:36 ` Segher Boessenkool
2022-05-03 2:00 ` [PATCH v2] " Alexandre Oliva
2022-05-06 16:14 ` Segher Boessenkool
2022-05-06 17:05 ` Jonathan Wakely
2022-05-06 18:24 ` [PATCH v3] " Alexandre Oliva
2022-04-28 13:56 ` [PATCH] " Matthias Kretz
2022-04-28 16:06 ` Segher Boessenkool [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220428160642.GT25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=m.kretz@gsi.de \
--cc=oliva@adacore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).