public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/110996] RISC-V vector Fortran: SEGV ICE during parsing
Date: Tue, 15 Aug 2023 01:54:48 +0000 [thread overview]
Message-ID: <bug-110996-4-PKFIAd1QuE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110996-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110996
--- Comment #4 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
(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 -Ofast
> testcase.f90
>
> The output I get is correct:
>
> testcase.f90:6:20:
>
> 6 | SUBROUTINE c(d) e
> | 1
> Error: Syntax error in SUBROUTINE statement at (1)
>
> Why does adding `v' to the -march string cause a SEGV?
I didn't reproduce the issue. What I see is GCC has ICE even without 'v' in
-march. And I have no idea for it.
next prev parent reply other threads:[~2023-08-15 1:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 15:59 [Bug fortran/110996] New: " jeremy.bennett at embecosm dot com
2023-08-12 2:35 ` [Bug fortran/110996] " juzhe.zhong at rivai dot ai
2023-08-13 19:35 ` anlauf at gcc dot gnu.org
2023-08-14 14:56 ` jeremy.bennett at embecosm dot com
2023-08-15 1:54 ` juzhe.zhong at rivai dot ai [this message]
2023-08-17 19:49 ` mikael at gcc dot gnu.org
2023-08-22 8:00 ` mikael at gcc dot gnu.org
2023-08-22 8:14 ` juzhe.zhong at rivai dot ai
2023-08-22 19:03 ` mikael at gcc dot gnu.org
2023-08-26 20:04 ` mikael at gcc dot gnu.org
2023-09-12 8:24 ` cvs-commit at gcc dot gnu.org
2023-09-12 8:33 ` mikael at gcc dot gnu.org
2023-09-15 17:27 ` mikael 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-110996-4-PKFIAd1QuE@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).