public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vineetg at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112817] New: RISC-V: RVV: provide a preprocessor macro for VLS codegen Date: Fri, 01 Dec 2023 21:50:06 +0000 [thread overview] Message-ID: <bug-112817-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817 Bug ID: 112817 Summary: RISC-V: RVV: provide a preprocessor macro for VLS codegen Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: vineetg at gcc dot gnu.org CC: ewlu at rivosinc dot com, juzhe.zhong at rivai dot ai, rdapp at gcc dot gnu.org Target Milestone: --- LLVM toggle for setting up fixed vector length using -mrvv-vector-bits=zvl (which in turn derives VL from -march=...-vl256) also generates a preprocessor define __riscv_v_fixed_vlen. gcc doesn't, which is a bit of pain for downstream projects such as xsimd. Granted the C-API document [1] doesn't specify this, generation by llvm and more importantly usage in downstream projects seems good enough of a requirement to have it in gcc as well. [1] https://github.com/riscv-non-isa/riscv-c-api-doc/blob/master/riscv-c-api.md
next reply other threads:[~2023-12-01 21:50 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-01 21:50 vineetg at gcc dot gnu.org [this message] 2023-12-01 21:51 ` [Bug target/112817] " pinskia at gcc dot gnu.org 2023-12-01 21:53 ` pinskia at gcc dot gnu.org 2023-12-01 21:55 ` pinskia at gcc dot gnu.org 2023-12-01 21:57 ` vineetg at gcc dot gnu.org 2023-12-01 22:01 ` pinskia at gcc dot gnu.org 2023-12-01 22:31 ` juzhe.zhong at rivai dot ai 2023-12-01 23:22 ` vineetg at gcc dot gnu.org 2023-12-01 23:24 ` juzhe.zhong at rivai dot ai 2023-12-05 15:59 ` kito at gcc dot gnu.org 2024-01-08 23:18 ` vineetg at gcc dot gnu.org 2024-01-08 23:21 ` [Bug target/112817] RISC-V: RVV: provide attribute riscv_rvv_vector_bits " juzhe.zhong at rivai dot ai 2024-01-08 23:41 ` pinskia at gcc dot gnu.org 2024-01-10 11:35 ` juzhe.zhong at rivai dot ai 2024-01-11 16:15 ` vineetg at gcc dot gnu.org 2024-03-06 18:23 ` vineetg at gcc dot gnu.org 2024-03-06 18:25 ` vineetg 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-112817-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).