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/104649] New: ICE in gfc_match_formal_arglist, at fortran/decl.cc:6733 Date: Tue, 22 Feb 2022 19:34:30 +0000 [thread overview] Message-ID: <bug-104649-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104649 Bug ID: 104649 Summary: ICE in gfc_match_formal_arglist, at fortran/decl.cc:6733 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: --- Affects versions down to r6 : $ cat z1.f90 module m interface module subroutine s(x) real :: x end end interface end submodule(m) m2 contains module subroutine s(*) end end $ cat z2.f90 module m interface module subroutine s(*) end end interface end submodule(m) m2 contains module subroutine s(x) real :: x end end $ gfortran-12-20220220 -c z1.f90 f951: internal compiler error: Segmentation fault 0xcc909f crash_signal ../../gcc/toplev.cc:322 0x6d9f81 gfc_match_formal_arglist(gfc_symbol*, int, int, bool) ../../gcc/fortran/decl.cc:6733 0x6dfaaf gfc_match_subroutine() ../../gcc/fortran/decl.cc:7957 0x74bb57 decode_statement ../../gcc/fortran/parse.cc:384 0x74d54a next_free ../../gcc/fortran/parse.cc:1397 0x74d54a next_statement ../../gcc/fortran/parse.cc:1629 0x751f8c parse_contained ../../gcc/fortran/parse.cc:6039 0x752e17 parse_module ../../gcc/fortran/parse.cc:6466 0x753147 gfc_parse_file() ../../gcc/fortran/parse.cc:6773 0x7a0a5f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:216
next reply other threads:[~2022-02-22 19:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-22 19:34 gscfq@t-online.de [this message] 2022-02-24 15:31 ` [Bug fortran/104649] ICE in gfc_match_formal_arglist, at fortran/decl.cc:6733 since r6-1958-g4668d6f9c00d4767 marxin at gcc dot gnu.org 2022-05-17 17:44 ` kargl at gcc dot gnu.org 2023-07-09 17:59 ` pault at gcc dot gnu.org 2023-10-24 20:16 ` anlauf at gcc dot gnu.org 2023-10-26 20:44 ` anlauf at gcc dot gnu.org 2023-10-27 17:18 ` cvs-commit at gcc dot gnu.org 2023-10-27 17:50 ` sgk at troutmask dot apl.washington.edu 2023-10-27 18:51 ` 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-104649-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).