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/99036] New: [11 Regression] ICE in gfc_current_interface_head, at fortran/interface.c:4699 Date: Tue, 09 Feb 2021 17:44:48 +0000 [thread overview] Message-ID: <bug-99036-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99036 Bug ID: 99036 Summary: [11 Regression] ICE in gfc_current_interface_head, at fortran/interface.c:4699 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: --- Changed between 20210117 and 20210124 : $ cat z1.f90 module m contains module procedure s end end $ gfortran-11-20210117 -c z1.f90 z1.f90:3:20: 3 | module procedure s | 1 Error: MODULE PROCEDURE at (1) must be in a generic module interface $ gfortran-11-20210207 -c z1.f90 f951: internal compiler error: in gfc_current_interface_head, at fortran/interface.c:4699 0x69b474 gfc_current_interface_head() ../../gcc/fortran/interface.c:4699 0x6777e5 gfc_match_modproc() ../../gcc/fortran/decl.c:9883 0x6db9c1 match_word ../../gcc/fortran/parse.c:65 0x6dfe30 decode_statement ../../gcc/fortran/parse.c:522 0x6e097c next_free ../../gcc/fortran/parse.c:1316 0x6e097c next_statement ../../gcc/fortran/parse.c:1548 0x6e511c parse_contained ../../gcc/fortran/parse.c:5743 0x6e5fd7 parse_module ../../gcc/fortran/parse.c:6170 0x6e6307 gfc_parse_file() ../../gcc/fortran/parse.c:6473 0x732e7f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:212
next reply other threads:[~2021-02-09 17:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-09 17:44 gscfq@t-online.de [this message] 2021-02-10 2:01 ` [Bug fortran/99036] " kargl at gcc dot gnu.org 2021-02-10 7:23 ` rguenth at gcc dot gnu.org 2021-02-10 9:09 ` marxin at gcc dot gnu.org 2021-04-27 11:40 ` [Bug fortran/99036] [11/12 " jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2021-11-10 18:01 ` gscfq@t-online.de 2021-11-10 21:04 ` kargl at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-03-20 20:36 ` [Bug fortran/99036] [11/12/13 " anlauf at gcc dot gnu.org 2023-03-20 20:40 ` anlauf at gcc dot gnu.org 2023-03-20 20:58 ` anlauf at gcc dot gnu.org 2023-03-21 19:01 ` cvs-commit at gcc dot gnu.org 2023-03-22 18:00 ` cvs-commit at gcc dot gnu.org 2023-03-24 18:41 ` cvs-commit at gcc dot gnu.org 2023-03-24 18:43 ` 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-99036-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).