From: Vineet Gupta <vineetg@rivosinc.com>
To: Patrick O'Neill <patrick@rivosinc.com>, gcc-patches@gcc.gnu.org
Cc: gkm@rivosinc.com, jeffreyalaw@gmail.com, ewlu@rivosinc.com
Subject: Re: [PATCH 1/2] RISC-V: add option -m(no-)autovec-segment
Date: Tue, 28 May 2024 15:03:52 -0700 [thread overview]
Message-ID: <97b9980e-4880-4e95-9d0a-da6d6390cd48@rivosinc.com> (raw)
In-Reply-To: <20240528215557.1192875-2-patrick@rivosinc.com>
On 5/28/24 14:55, Patrick O'Neill wrote:
> From: Greg McGary <gkm@rivosinc.com>
>
> Add option -m(no-)autovec-segment to enable/disable autovectorizer
> from emitting vector segment load/store instructions. This is useful for
> performance experiments.
>
> gcc/ChangeLog:
> * config/riscv/autovec.md (vec_mask_len_load_lanes, vec_mask_len_store_lanes):
> Predicate with TARGET_VECTOR_AUTOVEC_SEGMENT
> * gcc/config/riscv/riscv-opts.h (TARGET_VECTOR_AUTOVEC_SEGMENT): New macro.
> * gcc/config/riscv/riscv.opt (-m(no-)autovec-segment): New option.
> * gcc/tree-vect-stmts.cc (gcc/tree-vect-stmts.cc): Prevent divide-by-zero.
I think this middle-end change needs to be broken out, even if
eventually merged when committing, with its own test case.
-Vineet
next prev parent reply other threads:[~2024-05-28 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 21:55 [PATCH 0/2] RISC-V: Add -m(no-)autovec-segment option Patrick O'Neill
2024-05-28 21:55 ` [PATCH 1/2] RISC-V: add option -m(no-)autovec-segment Patrick O'Neill
2024-05-28 22:03 ` Vineet Gupta [this message]
2024-05-29 13:19 ` Robin Dapp
2024-05-28 21:55 ` [PATCH 2/2] RISC-V: Fix testcases renamed test flag options Patrick O'Neill
2024-05-28 22:05 ` Vineet Gupta
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=97b9980e-4880-4e95-9d0a-da6d6390cd48@rivosinc.com \
--to=vineetg@rivosinc.com \
--cc=ewlu@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gkm@rivosinc.com \
--cc=jeffreyalaw@gmail.com \
--cc=patrick@rivosinc.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).