[Bug target/111295] RISC-V vector ICE in vsetvl pass

2023-09-08 Thread jeremy.bennett at embecosm dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295 Jeremy Bennett changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug target/111295] RISC-V vector ICE in vsetvl pass

2023-09-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295 --- Comment #6 from CVS Commits --- The master branch has been updated by Pan Li : https://gcc.gnu.org/g:1b4c70d4271a00514ae20970d483c3b78d9d66ef commit r14-3743-g1b4c70d4271a00514ae20970d483c3b78d9d66ef Author: Juzhe-Zhong Date: Wed Sep 6

[Bug target/111295] RISC-V vector ICE in vsetvl pass

2023-09-06 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295 --- Comment #5 from JuzheZhong --- I see. A candidate patch to fix this issue: https://gcc.gnu.org/pipermail/gcc-patches/2023-September/629456.html

[Bug target/111295] RISC-V vector ICE in vsetvl pass

2023-09-06 Thread jeremy.bennett at embecosm dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295 --- Comment #4 from Jeremy Bennett --- @JuzheZhong - it's a C test case, not C++. Look like you are trying to compile it as C++.

[Bug target/111295] RISC-V vector ICE in vsetvl pass

2023-09-06 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295 --- Comment #3 from JuzheZhong --- This code can not be compiled: cc1plus: warning: command-line option '-Wno-implicit-function-declaration' is valid for C/ObjC but not for C++ bug.C: In function 'int q()': bug.C:6:9: warning: empty

[Bug target/111295] RISC-V vector ICE in vsetvl pass

2023-09-06 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295 JuzheZhong changed: What|Removed |Added CC||juzhe.zhong at rivai dot ai --- Comment

[Bug target/111295] RISC-V vector ICE in vsetvl pass

2023-09-05 Thread jeremy.bennett at embecosm dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295 --- Comment #1 from Jeremy Bennett --- Further analysis suggests this also causes the following SPEC CPU 2017 benchmarks to fail: 602.gcc_s, 648.exchange2_s, 607.cactuBSSN_s, 621.wrf_s, 627.cam4_s, 628.pop2_s, 638.imagick_s, 649.fotonik3d_s and