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/109312] Missing __riscv_v_intrinsic Date: Tue, 28 Mar 2023 15:00:26 +0000 [thread overview] Message-ID: <bug-109312-4-BqhgvBOz2o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109312-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109312 --- Comment #3 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:5a923516ae61ddc6dd863891db13189cbf392411 commit r13-6909-g5a923516ae61ddc6dd863891db13189cbf392411 Author: Kito Cheng <kito.cheng@sifive.com> Date: Tue Mar 28 22:21:50 2023 +0800 RISC-V: Define __riscv_v_intrinsic [PR109312] RVV intrinsic has defined a macro to identity the version of RVV intrinsic spec, we missed that before, thanksful we are catch this before release. gcc/ChangeLog: PR target/109312 * config/riscv/riscv-c.cc (riscv_ext_version_value): New. (riscv_cpu_cpp_builtins): Define __riscv_v_intrinsic and minor refactor. gcc/testsuite/ChangeLog: PR target/109312 * gcc.target/riscv/predef-__riscv_v_intrinsic.c: New test.
next prev parent reply other threads:[~2023-03-28 15:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-28 7:24 [Bug target/109312] New: " malat at debian dot org 2023-03-28 9:14 ` [Bug target/109312] " schwab@linux-m68k.org 2023-03-28 9:34 ` malat at debian dot org 2023-03-28 15:00 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-28 15:01 ` kito at gcc dot gnu.org
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-109312-4-BqhgvBOz2o@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).