public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pan2.li at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114639] [riscv] ICE in create_pre_exit, at mode-switching.cc:451
Date: Tue, 09 Apr 2024 01:33:15 +0000 [thread overview]
Message-ID: <bug-114639-4-usTQyD2rjD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114639-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114639
--- Comment #5 from Li Pan <pan2.li at intel dot com> ---
(In reply to Kito Cheng from comment #4)
> Reduced case:
> ```c
> typedef long c;
> #pragma riscv intrinsic "vector"
> template <unsigned long> struct d {};
> struct e {
> using f = d<0>;
> };
> struct g {
> using f = e::f;
> };
> template <typename, int> using h = g::f;
> template <unsigned long i> long k(d<i>);
> vbool16_t j(vuint64m4_t a) {
> c b;
> return __riscv_vmsne_vx_u64m4_b16(a, b, k(h<c, 2>()));
> }
>
> ```
Thanks Kito, reproduced on reduced case with option "riscv64-unknown-elf-g++
-O2 -march=rv64gcv". will take a look into it.
during RTL pass: mode_sw
test.c: In function ‘vbool16_t j(vuint64m4_t)’:
test.c:15:1: internal compiler error: in create_pre_exit, at
mode-switching.cc:451
15 | }
| ^
0x3978f12 create_pre_exit
/home/pli/gcc/555/riscv-gnu-toolchain/gcc/__RISCV_BUILD__/../gcc/mode-switching.cc:451
0x3979e9e optimize_mode_switching
/home/pli/gcc/555/riscv-gnu-toolchain/gcc/__RISCV_BUILD__/../gcc/mode-switching.cc:849
0x397b9bc execute
/home/pli/gcc/555/riscv-gnu-toolchain/gcc/__RISCV_BUILD__/../gcc/mode-switching.cc:1324
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2024-04-09 1:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 12:29 [Bug target/114639] New: " schwab@linux-m68k.org
2024-04-08 14:08 ` [Bug target/114639] " kito at gcc dot gnu.org
2024-04-08 18:13 ` pinskia at gcc dot gnu.org
2024-04-09 1:26 ` pan2.li at intel dot com
2024-04-09 1:28 ` kito at gcc dot gnu.org
2024-04-09 1:33 ` pan2.li at intel dot com [this message]
2024-04-09 1:37 ` juzhe.zhong at rivai dot ai
2024-04-09 3:45 ` pan2.li at intel dot com
2024-04-09 7:22 ` pan2.li at intel dot com
2024-04-09 8:05 ` ubizjak at gmail dot com
2024-04-09 8:32 ` pan2.li at intel dot com
2024-04-09 11:55 ` pan2.li at intel dot com
2024-04-09 15:30 ` pan2.li at intel dot com
2024-04-10 3:20 ` pan2.li at intel dot com
2024-04-11 3:02 ` cvs-commit at gcc dot gnu.org
2024-04-16 8:47 ` schwab@linux-m68k.org
2024-04-22 22:53 ` juzhe.zhong at rivai dot ai
2024-04-28 6:02 ` pan2.li at intel dot com
2024-04-28 6:22 ` juzhe.zhong at rivai dot ai
2024-04-28 6:51 ` pan2.li at intel 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-114639-4-usTQyD2rjD@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).