public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/102595] New: ICE in var_element, at fortran/decl.c:298 Date: Mon, 04 Oct 2021 18:41:34 +0000 [thread overview] Message-ID: <bug-102595-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102595 Bug ID: 102595 Summary: ICE in var_element, at fortran/decl.c:298 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started with r10 : $ cat z1.f90 program p complex, parameter :: x(0) = 2 data x%im /3.0/ end $ cat z2.f90 program p complex, parameter :: x(1) = 2 data x%im /3.0/ end $ gfortran-12-20211003 -c z2.f90 z2.f90:3:12: 3 | data x%im /3.0/ | 1 Error: PARAMETER 'x' shall not appear in a DATA statement at (1) $ gfortran-12-20211003 -c z1.f90 f951: internal compiler error: Segmentation fault 0xd41bdf crash_signal ../../gcc/toplev.c:331 0x77b0ed var_element ../../gcc/fortran/decl.c:298 0x77d4c4 top_var_list ../../gcc/fortran/decl.c:338 0x77d4c4 gfc_match_data() ../../gcc/fortran/decl.c:655 0x7eb6f1 match_word ../../gcc/fortran/parse.c:65 0x7f065e decode_statement ../../gcc/fortran/parse.c:469 0x7f13ca next_free ../../gcc/fortran/parse.c:1384 0x7f13ca next_statement ../../gcc/fortran/parse.c:1616 0x7f2aeb parse_spec ../../gcc/fortran/parse.c:4151 0x7f58bc parse_progunit ../../gcc/fortran/parse.c:6117 0x7f7041 gfc_parse_file() ../../gcc/fortran/parse.c:6658 0x843f3f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:216
next reply other threads:[~2021-10-04 18:41 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-04 18:41 gscfq@t-online.de [this message] 2021-10-05 20:00 ` [Bug fortran/102595] " anlauf at gcc dot gnu.org 2021-10-11 8:17 ` [Bug fortran/102595] ICE in var_element, at fortran/decl.c:298 since r10-5607-gde89b5748d68b76b marxin at gcc dot gnu.org 2021-12-23 20:13 ` kargl at gcc dot gnu.org 2021-12-23 20:15 ` kargl at gcc dot gnu.org 2021-12-23 23:20 ` kargl at gcc dot gnu.org 2022-12-30 3:26 ` cvs-commit at gcc dot gnu.org 2023-01-14 3:31 ` jvdelisle at gcc dot gnu.org 2023-01-15 20:07 ` jvdelisle at gcc dot gnu.org 2023-01-15 20:17 ` sgk at troutmask dot apl.washington.edu 2023-01-18 4:16 ` jvdelisle at gcc dot gnu.org 2023-01-21 23:24 ` cvs-commit at gcc dot gnu.org 2023-01-29 4:25 ` jvdelisle 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-102595-4@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: linkBe 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).