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/95342] New: [9/10/11 Regression] ICE in gfc_match_subroutine, at fortran/decl.c:7913
Date: Tue, 26 May 2020 16:45:41 +0000	[thread overview]
Message-ID: <bug-95342-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95342

            Bug ID: 95342
           Summary: [9/10/11 Regression] ICE in gfc_match_subroutine, at
                    fortran/decl.c:7913
           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 20191013 and 20191020, with a name conflict :


$ cat z1.f90
module m
   interface
      module subroutine s()
      end
      subroutine s() bind(c)
      end
   end interface
end


$ gfortran-11-20200524 -c z1.f90
f951: internal compiler error: Segmentation fault
0xbc0f6f crash_signal
        ../../gcc/toplev.c:328
0x644307 gfc_match_subroutine()
        ../../gcc/fortran/decl.c:7913
0x6a8427 decode_statement
        ../../gcc/fortran/parse.c:382
0x6a9e1a next_free
        ../../gcc/fortran/parse.c:1279
0x6a9e1a next_statement
        ../../gcc/fortran/parse.c:1511
0x6aba5c parse_interface
        ../../gcc/fortran/parse.c:3519
0x6aba5c parse_spec
        ../../gcc/fortran/parse.c:3875
0x6af43e parse_module
        ../../gcc/fortran/parse.c:6115
0x6af787 gfc_parse_file()
        ../../gcc/fortran/parse.c:6428
0x6fb9af gfc_be_parse_file
        ../../gcc/fortran/f95-lang.c:210

             reply	other threads:[~2020-05-26 16:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 16:45 gscfq@t-online.de [this message]
2020-05-26 16:46 ` [Bug fortran/95342] " gscfq@t-online.de
2020-05-26 18:16 ` kargl at gcc dot gnu.org
2020-05-26 18:29 ` kargl at gcc dot gnu.org
2020-05-27  7:38 ` rguenth at gcc dot gnu.org
2020-06-09 10:54 ` dominiq at lps dot ens.fr
2020-11-26 21:27 ` anlauf at gcc dot gnu.org
2020-12-03 19:33 ` cvs-commit at gcc dot gnu.org
2020-12-04 22:18 ` cvs-commit at gcc dot gnu.org
2020-12-04 22:31 ` cvs-commit at gcc dot gnu.org
2020-12-04 22:33 ` 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-95342-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: 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).