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] Missing __riscv_v_intrinsic
Date: Tue, 28 Mar 2023 09:34:19 +0000 [thread overview]
Message-ID: <bug-109312-4-QoGcUOa9LV@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 #2 from Mathieu Malaterre <malat at debian dot org> ---
(In reply to Andreas Schwab from comment #1)
> You need at least enable the V extension (-march=rv64gcv).
Oh, right ! Here is the correct full listing this time:
% /usr/lib/gcc-snapshot/bin/gcc -march=rv64gcv -Wp,-dM -E -c - < /dev/null |
grep risc
#define __riscv 1
#define __riscv_atomic 1
#define __riscv_v_elen_fp 64
#define __riscv_zvl32b 1000000
#define __riscv_cmodel_medlow 1
#define __riscv_zve64d 1000000
#define __riscv_zve64f 1000000
#define __riscv_zve64x 1000000
#define __riscv_mul 1
#define __riscv_muldiv 1
#define __riscv_xlen 64
#define __riscv_zve32f 1000000
#define __riscv_zve32x 1000000
#define __riscv_zvl128b 1000000
#define __riscv_fsqrt 1
#define __riscv_v_min_vlen 128
#define __riscv_v_elen 64
#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_v 1000000
#define __riscv_zicsr 2000000
#define __riscv_compressed 1
#define __riscv_vector 1
#define __riscv_float_abi_double 1
#define __riscv_flen 64
#define __riscv_arch_test 1
#define __riscv_zvl64b 1000000
#define __riscv_div 1
#define __riscv_zifencei 2000000
next prev parent reply other threads:[~2023-03-28 9:34 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 [this message]
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-QoGcUOa9LV@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: link
Be 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).