public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112817] RISC-V: RVV: provide a preprocessor macro for VLS codegen
Date: Fri, 01 Dec 2023 22:01:33 +0000 [thread overview]
Message-ID: <bug-112817-4-rcfDbP4VGE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112817-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Vineet Gupta from comment #3)
> I agree, but what xsimd does is not under our control. Whoever wants to use
> xsimd for whatever reasons, we can allow gcc to be used similarly to llvm
> and certainly not for lack of a trivial define.
What I am trying to say is almost all of these "SIMD" libraries were done to
wrap x86_64 SIMD and is almost done in a bad form in general. I noticed that
when working on AARCH64 (even before SVE). they push the idea of a low level
wrapper just because "it is easier" rather than higher level concepts. xsimd,
even the whole C++ SIMD library seems to push low level wrappers rather than
high level concepts that could be optimized.
next prev parent reply other threads:[~2023-12-01 22:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 21:50 [Bug target/112817] New: " vineetg at gcc dot gnu.org
2023-12-01 21:51 ` [Bug target/112817] " pinskia at gcc dot gnu.org
2023-12-01 21:53 ` pinskia at gcc dot gnu.org
2023-12-01 21:55 ` pinskia at gcc dot gnu.org
2023-12-01 21:57 ` vineetg at gcc dot gnu.org
2023-12-01 22:01 ` pinskia at gcc dot gnu.org [this message]
2023-12-01 22:31 ` juzhe.zhong at rivai dot ai
2023-12-01 23:22 ` vineetg at gcc dot gnu.org
2023-12-01 23:24 ` juzhe.zhong at rivai dot ai
2023-12-05 15:59 ` kito at gcc dot gnu.org
2024-01-08 23:18 ` vineetg at gcc dot gnu.org
2024-01-08 23:21 ` [Bug target/112817] RISC-V: RVV: provide attribute riscv_rvv_vector_bits " juzhe.zhong at rivai dot ai
2024-01-08 23:41 ` pinskia at gcc dot gnu.org
2024-01-10 11:35 ` juzhe.zhong at rivai dot ai
2024-01-11 16:15 ` vineetg at gcc dot gnu.org
2024-03-06 18:23 ` vineetg at gcc dot gnu.org
2024-03-06 18:25 ` vineetg at gcc dot gnu.org
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=bug-112817-4-rcfDbP4VGE@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).