public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Matthias Kretz <m.kretz@gsi.de>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Rewrite or avoid casts to 64-bit element types
Date: Tue, 6 Jun 2023 16:54:47 +0100	[thread overview]
Message-ID: <CACb0b4kazm6BNV+0T51aVkEHOZNYOV1MPPOG-+3UACR2WsWFLA@mail.gmail.com> (raw)
In-Reply-To: <4608206.VLH7GnMWUR@minbar>

[-- Attachment #1: Type: text/plain, Size: 2206 bytes --]

On Tue, 6 Jun 2023 at 15:14, Matthias Kretz via Libstdc++ <
libstdc++@gcc.gnu.org> wrote:

> Last part to resolve test failure introduced with PR109822.
>
> OK for master and backports (gcc-11 doesn't have __builtin_shufflevector,
> though)?
>

Yep, OK.



>
> Tested on x86_64-pc-linux-gnu and powerpc64le-linux-gnu
>
> ----- >8 -----
>
> Fix SFINAE on __is_intrinsic_type for 64-bit element types on non-VSX
> POWER targets.
>
> Replace __extract_part implementation (which was the only user of
> __shift_elements_right) by relying on __builtin_shufflevector (not
> available in GCC 11). This removes another cast to 64-bit element type,
> which breaks on non-VSX POWER.
>
> Signed-off-by: Matthias Kretz <m.kretz@gsi.de>
>
> libstdc++-v3/ChangeLog:
>
>         PR libstdc++/109822
>         * include/experimental/bits/simd.h: Include <bits/stl_algo.h>
>         for min(initializer_list).
>         Define __intrinsic_type_impl for all vectorizable types, but
>         without type member, if the target doesn't support it.
>         * include/experimental/bits/simd_builtin.h (__idx_permute): New.
>         (__shift_elements_right): Removed.
>         (__extract_part): Rewrite using __idx_permute.
>         (_S_reduce): Avoid unconditional cast to 64-bit element type
>         when the element type is known to be smaller.
> ---
>  libstdc++-v3/include/experimental/bits/simd.h |  34 ++-
>  .../include/experimental/bits/simd_builtin.h  | 250 +++++-------------
>  2 files changed, 96 insertions(+), 188 deletions(-)
>
>
> --
> ──────────────────────────────────────────────────────────────────────────
>  Dr. Matthias Kretz                           https://mattkretz.github.io
>  GSI Helmholtz Centre for Heavy Ion Research               https://gsi.de
>  stdₓ::simd
> ──────────────────────────────────────────────────────────────────────────

      reply	other threads:[~2023-06-06 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 14:13 Matthias Kretz
2023-06-06 15:54 ` Jonathan Wakely [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=CACb0b4kazm6BNV+0T51aVkEHOZNYOV1MPPOG-+3UACR2WsWFLA@mail.gmail.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=m.kretz@gsi.de \
    /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).