From: Michael Collison <collison@rivosinc.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH v2 00/07] RISC-V: autovec: Add auto-vectorization support
Date: Sun, 5 Mar 2023 22:13:16 -0500 [thread overview]
Message-ID: <6ffdeeb4-8523-03f7-eb30-ee3e5886afad@rivosinc.com> (raw)
This series of patches adds foundational support for RISC-V
autovectorization support. These patches are based on the current
upstream rvv vector intrinsic support and is not a new implementation.
Most of the implementation consists of adding the new vector cost model,
the autovectorization patterns themselves and target hooks.This
implementation only provides support for integer addition and
subtraction as a proof of concept. This patch set should not be
construed to be feature complete. Based on conversations with the
community these patches are intended to lay the groundwork for feature
completion and collaboration within the RISC-V community.In version 1 of
this patch submission I neglected to indicate that these patches are
largely based off the work of Juzhe Zhong
(juzhe.zhong@rivai.ai<mailto:juzhe.zhong@rivai.ai>) of RiVAI. More
specifically the rvv-next branch
at:https://github.com/riscv-collab/riscv-gcc.git
<https://github.com/riscv-collab/riscv-gcc.git>is the foundation of this
patch set. I want to publicly apologize to Juzhe and RiVIA for not
attributing their work visibly and publicly.As discussed on this list,
if these patches are approved they will be merged into a
"auto-vectorization" branch once gcc-13 branches for release.There are
two known issues related to crashes (assert failures) associated with
tree vectorization; one of which I have sent a patch for and have
received feedback.
Changes in v2
- Updated ChangeLog entry to include RiVAI contributions
- Fixed ChangeLog email formatting
- Fixed gnu formatting issues in the code
next reply other threads:[~2023-03-06 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 3:13 Michael Collison [this message]
2023-03-06 4:05 ` Xi Ruoyao
2023-03-06 5:26 ` Michael Collison
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=6ffdeeb4-8523-03f7-eb30-ee3e5886afad@rivosinc.com \
--to=collison@rivosinc.com \
--cc=gcc-patches@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).