From: Matthias Kretz <m.kretz@gsi.de>
To: Tejas Belagod <tejas.belagod@arm.com>,
Richard Biener <richard.guenther@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] GNU Vector Extension -- Packed Boolean Vectors
Date: Thu, 5 Oct 2023 14:48:26 -0600 [thread overview]
Message-ID: <3579609.iZASKD2KPV@minbar> (raw)
In-Reply-To: <CAFiYyc15ZGB+bRJs9DTmXT6jKWPoH117SFgR4RSMj0oW1qAHDw@mail.gmail.com>
On Wednesday, 26 July 2023 06:33:41 MDT Richard Biener wrote:
> Btw, how the experimental SIMD C++ standard library handles
> these issue might be also interesting to research (author CCed)
I only skimmed over this thread now. FWIW, I would really like better
support for AVX-512 bitmasks for the std::experimental::simd implementation
(std::simd for C++26). I probably want better support for all the other
targets that use bitmasks - but so far I only have experience with AVX512.
To make the AVX512 implementation of std::experimental::simd efficient I
have to call intrinsics/builtins instead of directly expressing what I want
to do using the [[gnu::vector_size]] types. There are some instances where
I have to convert between bitmask and element-sized mask vectors - and to
make that efficient I call all kinds of intrinsics/builtins. And from what
I've seen, a bitmask -> mask vector -> bitmask conversion won't be
recognized as a no-op (the other way around, as well).
At this point I have no technical input to this thread. But if there's
anything you want me to test - whether it helps in the simd implementation
- let me know.
-Matthias
--
──────────────────────────────────────────────────────────────────────────
Dr. Matthias Kretz https://mattkretz.github.io
GSI Helmholtz Center for Heavy Ion Research https://gsi.de
std::simd
──────────────────────────────────────────────────────────────────────────
prev parent reply other threads:[~2023-10-05 20:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 6:23 Tejas Belagod
2023-06-26 8:50 ` Richard Biener
2023-06-27 6:30 ` Tejas Belagod
2023-06-27 7:28 ` Richard Biener
2023-06-28 11:26 ` Tejas Belagod
2023-06-29 13:25 ` Richard Biener
2023-07-03 6:50 ` Tejas Belagod
2023-07-03 8:01 ` Richard Biener
2023-07-13 10:14 ` Tejas Belagod
2023-07-13 10:35 ` Richard Biener
2023-07-14 10:18 ` Tejas Belagod
2023-07-17 12:16 ` Richard Biener
2023-07-26 7:21 ` Tejas Belagod
2023-07-26 12:26 ` Richard Biener
2023-07-26 12:33 ` Richard Biener
2023-10-05 20:48 ` Matthias Kretz [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=3579609.iZASKD2KPV@minbar \
--to=m.kretz@gsi.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=tejas.belagod@arm.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).