public inbox for
 help / color / mirror / Atom feed
From: "" <>
To: jeffreyalaw <>,
	 gcc-patches <>
Cc: kito.cheng <>,  palmer <>
Subject: Re: Re: [PATCH] RISC-V: Add RVV auto-vectorization compile option
Date: Tue, 25 Apr 2023 14:08:27 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]

Ideally, LMUL should be dynamically picked by compiler according to the user codes.

However, GCC doesn't support it yet and it's not a easy feature to be supported in the future.

My plan is that we let LMUL picked statically according to compile option 
and we fully support and test LMUL = 1/2/4/8 so far.
Then we can support the feature of picking LMUL during auto-vectorization in the future when we figure out how to do that.
From: Jeff Law
Date: 2023-04-25 14:00
To: juzhe.zhong; gcc-patches
CC: kito.cheng; palmer
Subject: Re: [PATCH] RISC-V: Add RVV auto-vectorization compile option
On 4/6/23 19:21, wrote:
> From: Juzhe-Zhong <>
> The next patch to enable basic RVV auto-vectorization of
> VLA auto-vectorization (RVV_SCALABLE) and fixed-length VLS auto-vectorization (RVV_FIXED_VLMAX).
> We will support RVV_FIXED_VLMIN in the future.
> gcc/ChangeLog:
>          * config/riscv/riscv-opts.h (enum riscv_autovec_preference_enum): Add RVV auto-vectorization compile option.
>          (enum riscv_autovec_lmul_enum): Ditto.
>          * config/riscv/riscv.opt: Ditto.
No real objection here.  Just a question.   What's the rationale behind 
exposing lmul settings to the user?  I'd think that should largely be 
compiler managed.  But maybe I'm missing something.

      reply	other threads:[~2023-04-25  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07  1:21 juzhe.zhong
2023-04-25  6:00 ` Jeff Law
2023-04-25  6:08   ` juzhe.zhong [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).