public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109544] implicit declaration of function '__riscv_vsseg4e8_v_i8mf8' Date: Tue, 18 Apr 2023 14:10:27 +0000 [thread overview] Message-ID: <bug-109544-4-jr5ItaPSk4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109544-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109544 --- Comment #1 from JuzheZhong <juzhe.zhong at rivai dot ai> --- We don't support segment yet since segment load/store api will be changed. For example: The old api: __riscv_vsseg4e8_v_i8mf8(base, vint8mf8_t v0, vint8mf8_t v1, vint8mf8_t v2, vint8mf8_t v3, vl); will be changed into: __riscv_vsseg4e8_v_i8mf8(base, vint8mf8x4_t v0, vl); The latest segment load/store are not merged yet: https://github.com/riscv-non-isa/rvv-intrinsic-doc/pull/198 but will be soon merged. GCC will not implement old api, instead we are implementing latest api recently and they are expected in GCC 14.
next prev parent reply other threads:[~2023-04-18 14:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-18 14:04 [Bug target/109544] New: " malat at debian dot org 2023-04-18 14:10 ` juzhe.zhong at rivai dot ai [this message] 2023-04-18 14:15 ` [Bug target/109544] " malat at debian dot org 2023-04-21 7:03 ` juzhe.zhong at rivai dot ai 2023-05-03 22:56 ` 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-109544-4-jr5ItaPSk4@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: 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).