public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/116484] Allow constexpr expression in riscv_rvv_vector_bits attribute
Date: Mon, 26 Aug 2024 09:11:06 +0000	[thread overview]
Message-ID: <bug-116484-4-FKHlekl1nN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-116484-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116484

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://github.com/riscv-no
                   |                            |n-isa/rvv-intrinsic-doc/iss
                   |                            |ues/176

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The full documentation in the RVV documentation is not done so ....

  parent reply	other threads:[~2024-08-26  9:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26  8:21 [Bug c++/116484] New: " sergesanspaille at free dot fr
2024-08-26  8:28 ` [Bug c++/116484] " pinskia at gcc dot gnu.org
2024-08-26  9:11 ` pinskia at gcc dot gnu.org [this message]
2024-08-26  9:25 ` [Bug target/116484] Allow constexpr expression in riscv_rvv_vector_bits attribute and arm_sve_vector_bits pinskia at gcc dot gnu.org
2024-08-27 23:54 ` sayhappy at gmail dot com
2024-08-27 23:58 ` pinskia at gcc dot gnu.org
2024-08-28  0:01 ` pinskia at gcc dot gnu.org
2024-08-28  0:08 ` pinskia at gcc dot gnu.org
2024-08-28  3:42 ` sayhappy at gmail dot com

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-116484-4-FKHlekl1nN@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).