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/109228] warning: implicit declaration of function '__riscv_vlenb' Date: Thu, 23 Mar 2023 03:22:50 +0000 [thread overview] Message-ID: <bug-109228-4-bz4T8mVopJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109228-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109228 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kito Cheng <kito@gcc.gnu.org>: https://gcc.gnu.org/g:116a8678840f9f52ec14639ff07e302a8c429f32 commit r13-6822-g116a8678840f9f52ec14639ff07e302a8c429f32 Author: Ju-Zhe Zhong <juzhe.zhong@rivai.ai> Date: Wed Mar 22 13:06:23 2023 +0800 RISC-V: Implement __riscv_vlenb PR109228 __riscv_vlenb is defined in RVV intrinsic spec 0.11 and used in some project like google/highway. gcc/ChangeLog: PR target/109228 * config/riscv/riscv-vector-builtins-bases.cc (class vlenb): Add __riscv_vlenb support. (BASE): Ditto. * config/riscv/riscv-vector-builtins-bases.h: Ditto. * config/riscv/riscv-vector-builtins-functions.def (vlenb): Ditto. * config/riscv/riscv-vector-builtins-shapes.cc (struct vlenb_def): Ditto. (SHAPE): Ditto. * config/riscv/riscv-vector-builtins-shapes.h: Ditto. * config/riscv/riscv-vector-builtins.cc: Ditto. gcc/testsuite/ChangeLog: PR target/109228 * gcc.target/riscv/rvv/base/vlenb-1.c: New test.
next prev parent reply other threads:[~2023-03-23 3:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-21 8:54 [Bug c/109228] New: " malat at debian dot org 2023-03-21 10:27 ` [Bug c/109228] " kito at gcc dot gnu.org 2023-03-21 11:09 ` [Bug target/109228] " malat at debian dot org 2023-03-22 5:07 ` juzhe.zhong at rivai dot ai 2023-03-23 3:22 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-23 3:24 ` kito at gcc dot gnu.org 2023-03-23 6:58 ` jan.wassenberg 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-109228-4-bz4T8mVopJ@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).