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/99349] New: ICE in match_data_constant, at fortran/decl.c:426 Date: Tue, 02 Mar 2021 19:01:32 +0000 [thread overview] Message-ID: <bug-99349-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99349 Bug ID: 99349 Summary: ICE in match_data_constant, at fortran/decl.c:426 Product: gcc Version: 11.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 r9, between 20181028 and 20181104 : $ cat z1.f90 function f() logical, parameter :: a((1.)/0) = .true. integer :: b data b /a%kind/ end $ gfortran-11-20210228 -c z1.f90 f951: internal compiler error: Segmentation fault 0xc0666f crash_signal ../../gcc/toplev.c:327 0x66dab4 match_data_constant ../../gcc/fortran/decl.c:426 0x66dc63 top_val_list ../../gcc/fortran/decl.c:499 0x66df72 gfc_match_data() ../../gcc/fortran/decl.c:716 0x6d87e1 match_word ../../gcc/fortran/parse.c:65 0x6dca2e decode_statement ../../gcc/fortran/parse.c:469 0x6dd79c next_free ../../gcc/fortran/parse.c:1316 0x6dd79c next_statement ../../gcc/fortran/parse.c:1548 0x6dee0b parse_spec ../../gcc/fortran/parse.c:3967 0x6e1bdc parse_progunit ../../gcc/fortran/parse.c:5896 0x6e35e7 gfc_parse_file() ../../gcc/fortran/parse.c:6451 0x72fd7f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:212
next reply other threads:[~2021-03-02 19:01 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-02 19:01 gscfq@t-online.de [this message] 2021-03-03 1:35 ` [Bug fortran/99349] " kargl at gcc dot gnu.org 2021-03-03 7:55 ` marxin at gcc dot gnu.org 2022-09-01 19:57 ` anlauf at gcc dot gnu.org 2022-09-01 22:03 ` sgk at troutmask dot apl.washington.edu 2022-09-01 22:44 ` sgk at troutmask dot apl.washington.edu 2022-09-02 19:12 ` cvs-commit at gcc dot gnu.org 2022-09-02 19:21 ` anlauf 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-99349-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).