[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-09-15 Thread mikael at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 Mikael Morin changed: What|Removed |Added Target Milestone|--- |14.0

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-09-12 Thread mikael at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 Mikael Morin changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-09-12 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 --- Comment #10 from CVS Commits --- The master branch has been updated by Mikael Morin : https://gcc.gnu.org/g:b9cbd1a2c2f50d4e305938d97916011bd5839ce0 commit r14-3864-gb9cbd1a2c2f50d4e305938d97916011bd5839ce0 Author: Mikael Morin Date: Tu

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-26 Thread mikael at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 Mikael Morin changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |mikael at gcc dot gnu.org

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-22 Thread mikael at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 --- Comment #8 from Mikael Morin --- (In reply to JuzheZhong from comment #7) > Do you have a solution that we can fix RISC-V backend? No, this is not RISC-V specific. > Or you will fix it in Fortran front-end? Yes, the fix will have to be in

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-22 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 --- Comment #7 from JuzheZhong --- (In reply to Mikael Morin from comment #6) > (In reply to Mikael Morin from comment #5) > > Here sym->formal_ns is NULL because the symbol C has not been completely > > setup. > > This makes the following an "

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-22 Thread mikael at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 --- Comment #6 from Mikael Morin --- (In reply to Mikael Morin from comment #5) > Here sym->formal_ns is NULL because the symbol C has not been completely > setup. This makes the following an "obvious" fix: diff --git a/gcc/fortran/decl.cc b/g

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-17 Thread mikael at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 Mikael Morin changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-14 Thread juzhe.zhong at rivai dot ai via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 --- Comment #4 from JuzheZhong --- (In reply to Jeremy Bennett from comment #3) > @JuzheZhong I believe this is in someway related to RVV. If I remove `v' > from the march: > > riscv64-unknown-linux-gnu-gfortran -march=rv64gc -mabi=lp64d -c

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-14 Thread jeremy.bennett at embecosm dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 --- Comment #3 from Jeremy Bennett --- @JuzheZhong I believe this is in someway related to RVV. If I remove `v' from the march: riscv64-unknown-linux-gnu-gfortran -march=rv64gc -mabi=lp64d -c -Ofast testcase.f90 The output I get is correc

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

2023-08-13 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996 anlauf at gcc dot gnu.org changed: What|Removed |Added Keywords||error-recovery --- Comment #

[Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing

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