public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113420] risc-v vector: ICE when using C compiler compile C++ RVV intrinsics
Date: Mon, 22 Jan 2024 06:48:14 +0000	[thread overview]
Message-ID: <bug-113420-4-8xX1GoUWX7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113420-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Li Xu <xuli@gcc.gnu.org>:

https://gcc.gnu.org/g:46a664dd59ec6c1121914d6857d6edb94501c517

commit r14-8328-g46a664dd59ec6c1121914d6857d6edb94501c517
Author: xuli <xuli1@eswincomputing.com>
Date:   Mon Jan 22 06:41:49 2024 +0000

    RISC-V: Bugfix for resolve_overloaded_builtin[PR113420]

    v2:
    Avoid internal ICE for the case below.
    vint8mf8_t test_vle8_v_i8mf8_m(vbool64_t vm, const int32_t *rs1, size_t vl)
{
      return __riscv_vle8(vm, rs1, vl);
    }

    v1:
    Change the hash value of overloaded intrinsic from considering
    all parameter types to:
    1. Encoding vector data type
    2. In order to distinguish vle8_v_i8mf8_m(vbool64_t vm, const int8_t *rs1,
size_t vl)
       and vle8_v_u8mf8_m(vbool64_t vm, const uint8_t *rs1, size_t vl), encode
the pointer type
    3. In order to distinguish vfadd_vv_f32mf2_rm(vfloat32mf2_t vs2,
vfloat32mf2_t vs1, size_t vl)
       and vfadd_vv_f32mf2(vfloat32mf2_t vs2, vfloat32mf2_t vs1, size_t vl),
encode the number of
       parameters. The same goes for the vxrm intrinsics.

            PR target/113420

    gcc/ChangeLog:

            * config/riscv/riscv-vector-builtins.cc (has_vxrm_or_frm_p):remove.
            (registered_function::overloaded_hash):refactor.
            (resolve_overloaded_builtin):avoid internal ICE.

    gcc/testsuite/ChangeLog:

            * gcc.target/riscv/rvv/base/pr113420-1.c: New test.
            * gcc.target/riscv/rvv/base/pr113420-2.c: New test.

  reply	other threads:[~2024-01-22  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 11:23 [Bug c/113420] New: " juzhe.zhong at rivai dot ai
2024-01-22  6:48 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-22  7:12 ` [Bug target/113420] " juzhe.zhong at rivai dot ai

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-113420-4-8xX1GoUWX7@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).