public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kito Cheng <kito@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6486] RISC-V: Remove void_type_node of void_args for vsetvlmax intrinsic Date: Sun, 5 Mar 2023 09:17:24 +0000 (GMT) [thread overview] Message-ID: <20230305091724.00C0E3858280@sourceware.org> (raw) https://gcc.gnu.org/g:f8ba8a45edcff7fe117f88deff7184dffe3af311 commit r13-6486-gf8ba8a45edcff7fe117f88deff7184dffe3af311 Author: Ju-Zhe Zhong <juzhe.zhong@rivai.ai> Date: Mon Feb 27 16:01:32 2023 +0800 RISC-V: Remove void_type_node of void_args for vsetvlmax intrinsic This patch is to fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108927. PR108927 gcc/ChangeLog: * config/riscv/riscv-vector-builtins.cc: Remove void_type_node. Diff: --- gcc/config/riscv/riscv-vector-builtins.cc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/gcc/config/riscv/riscv-vector-builtins.cc b/gcc/config/riscv/riscv-vector-builtins.cc index a430104f1e7..af11758e9b4 100644 --- a/gcc/config/riscv/riscv-vector-builtins.cc +++ b/gcc/config/riscv/riscv-vector-builtins.cc @@ -291,9 +291,8 @@ static const rvv_type_info oextu_ops[] = { static CONSTEXPR const rvv_arg_type_info rvv_arg_type_info_end = rvv_arg_type_info (NUM_BASE_TYPES); -/* A list of args for size_t func (void) function. */ -static CONSTEXPR const rvv_arg_type_info void_args[] - = {rvv_arg_type_info (RVV_BASE_void), rvv_arg_type_info_end}; +/* A list of args for size_t func () function. */ +static CONSTEXPR const rvv_arg_type_info void_args[] = {rvv_arg_type_info_end}; /* A list of args for size_t func () function. */ static CONSTEXPR const rvv_arg_type_info end_args[]
reply other threads:[~2023-03-05 9:17 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=20230305091724.00C0E3858280@sourceware.org \ --to=kito@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).