public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vineetg at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112817] RISC-V: RVV: provide attribute riscv_rvv_vector_bits for VLS codegen
Date: Wed, 06 Mar 2024 18:25:05 +0000	[thread overview]
Message-ID: <bug-112817-4-0MbfHVNk7s@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 #15 from Vineet Gupta <vineetg at gcc dot gnu.org> ---
(In reply to Vineet Gupta from comment #14)
> 2. implement gcc toggle -mrvv-vector-bits=zvl which essentially copies the
> xxx from -march string

Done:

commit 0a01d1232ff0a8b094270fbf45c9fd0ea46df19f
Author: Pan Li <pan2.li@intel.com>
Date:   Fri Feb 23 15:37:28 2024 +0800

    RISC-V: Introduce gcc option mrvv-vector-bits for RVV

    This patch would like to introduce one new gcc option for RVV. To
    appoint the bits size of one RVV vector register. Valid arguments to
    '-mrvv-vector-bits=' are:

    * scalable
    * zvl

    The scalable will pick up the zvl*b in the march as the minimal vlen.
    For example, the minimal vlen will be 512 when march=rv64gcv_zvl512b
    and mrvv-vector-bits=scalable.

    The zvl will pick up the zvl*b in the march as exactly vlen.
    For example, the vlen will be 1024 exactly when march=rv64gcv_zvl1024b
    and mrvv-vector-bits=zvl.

    The internal option --param=riscv-autovec-preference will be replaced
    by option -mrvv-vector-bits. Aka:

    * -mrvv-vector-bits=scalable indicates
--param=riscv-autovec-preference=scalable
    * -mrvv-vector-bits=zvl indicates
--param=riscv-autovec-preference=fixed-vlmax

    You can also take -fno-tree-vectorize for
--param=riscv-autovec-preference=none.
    The internal option --param=riscv-autovec-preference is unavailable after
this
    patch.

      parent reply	other threads:[~2024-03-06 18:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 21:50 [Bug target/112817] New: RISC-V: RVV: provide a preprocessor macro " 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
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 [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:
  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-0MbfHVNk7s@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).