public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Collison <collison@rivosinc.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH 00/07] RISC-V: Add auto-vectorization support
Date: Thu, 2 Mar 2023 23:52:33 -0500	[thread overview]
Message-ID: <87e1164d-1377-8025-223e-7c377ae1752d@rivosinc.com> (raw)

This series of patches adds foundational support for RISC-V 
autovectorization. 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.

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. I will be sending a patch for the second 
issue tomorrow.


  gcc/common/config/riscv/riscv-common.cc       |   2 +-
  gcc/config.gcc                                |   2 +-
  gcc/config/riscv/predicates.md                |  13 +
  gcc/config/riscv/riscv-cores.def              |  14 +-
  gcc/config/riscv/riscv-opts.h                 |  40 ++
  gcc/config/riscv/riscv-protos.h               |  15 +
  gcc/config/riscv/riscv-v.cc                   | 178 ++++-
  gcc/config/riscv/riscv-vector-builtins.cc     |   4 +-
  gcc/config/riscv/riscv-vector-builtins.h      |   2 +
  gcc/config/riscv/riscv-vector-cost.cc         | 620 ++++++++++++++++++
  gcc/config/riscv/riscv-vector-cost.h          | 400 +++++++++++
  gcc/config/riscv/riscv.cc                     | 321 ++++++++-
  gcc/config/riscv/riscv.md                     |   1 +
  gcc/config/riscv/riscv.opt                    |  20 +
  gcc/config/riscv/t-riscv                      |   5 +
  gcc/config/riscv/vector-auto.md               | 172 +++++
  gcc/config/riscv/vector-iterators.md          |   2 +
  gcc/config/riscv/vector.md                    |   4 +-
  .../riscv/rvv/autovec/loop-add-rv32.c         |  24 +
  .../gcc.target/riscv/rvv/autovec/loop-add.c   |  24 +
  .../riscv/rvv/autovec/loop-sub-rv32.c         |  24 +
  .../gcc.target/riscv/rvv/autovec/loop-sub.c   |  24 +
  22 files changed, 1893 insertions(+), 18 deletions(-)
  create mode 100644 gcc/config/riscv/riscv-vector-cost.cc
  create mode 100644 gcc/config/riscv/riscv-vector-cost.h
  create mode 100644 gcc/config/riscv/vector-auto.md
  create mode 100644 
gcc/testsuite/gcc.target/riscv/rvv/autovec/loop-add-rv32.c
  create mode 100644 gcc/testsuite/gcc.target/riscv/rvv/autovec/loop-add.c
  create mode 100644 
gcc/testsuite/gcc.target/riscv/rvv/autovec/loop-sub-rv32.c
  create mode 100644 gcc/testsuite/gcc.target/riscv/rvv/autovec/loop-sub.c


                 reply	other threads:[~2023-03-03  4:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87e1164d-1377-8025-223e-7c377ae1752d@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).