public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "malat at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109312] New: Missing __riscv_v_intrinsic Date: Tue, 28 Mar 2023 07:24:25 +0000 [thread overview] Message-ID: <bug-109312-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109312 Bug ID: 109312 Summary: Missing __riscv_v_intrinsic Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: malat at debian dot org Target Milestone: --- Currently GCC is missing __riscv_v_intrinsic see: https://github.com/riscv-non-isa/rvv-intrinsic-doc/blob/master/version_macro.adoc For reference: % /usr/lib/gcc-snapshot/bin/gcc -Wp,-dM -E -c - < /dev/null | grep risc #define __riscv 1 #define __riscv_atomic 1 #define __riscv_cmodel_medlow 1 #define __riscv_mul 1 #define __riscv_muldiv 1 #define __riscv_xlen 64 #define __riscv_fsqrt 1 #define __riscv_m 2000000 #define __riscv_fdiv 1 #define __riscv_a 2001000 #define __riscv_c 2000000 #define __riscv_d 2002000 #define __riscv_f 2002000 #define __riscv_i 2001000 #define __riscv_zicsr 2000000 #define __riscv_compressed 1 #define __riscv_float_abi_double 1 #define __riscv_flen 64 #define __riscv_arch_test 1 #define __riscv_div 1 #define __riscv_zifencei 2000000
next reply other threads:[~2023-03-28 7:24 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-28 7:24 malat at debian dot org [this message] 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 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@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).