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/95880] New: [9/10/11 Regression] ICE in gfc_add_type, at fortran/symbol.c:2030
Date: Wed, 24 Jun 2020 18:52:03 +0000	[thread overview]
Message-ID: <bug-95880-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95880
           Summary: [9/10/11 Regression] ICE in gfc_add_type, at
                    fortran/symbol.c:2030
           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: ---

Affects versions down to r8, started between 20200517 and 20200524 :


$ cat z1.f90
module m
end
block data
   use m
   integer m
end block data


$ cat z5.f90
module m
   type t
   end type
end
block data
   use m
   type(t) m
end block data


$ gfortran-11-20200517 -c z1.f90
z1.f90:5:12:

    5 |    integer m
      |            1
Error: Symbol 'm' at (1) cannot have a type


$ gfortran-11-20200621 -c z1.f90
f951: internal compiler error: Segmentation fault
0xbce57f crash_signal
        ../../gcc/toplev.c:328
0x6f02bc gfc_add_type(gfc_symbol*, gfc_typespec*, locus*)
        ../../gcc/fortran/symbol.c:2030
0x63eeed build_sym
        ../../gcc/fortran/decl.c:1685
0x649969 variable_decl
        ../../gcc/fortran/decl.c:2793
0x649969 gfc_match_data_decl()
        ../../gcc/fortran/decl.c:6195
0x6ad323 match_word
        ../../gcc/fortran/parse.c:65
0x6ad323 decode_statement
        ../../gcc/fortran/parse.c:376
0x6aed6a next_free
        ../../gcc/fortran/parse.c:1280
0x6aed6a next_statement
        ../../gcc/fortran/parse.c:1512
0x6b03bb parse_spec
        ../../gcc/fortran/parse.c:3923
0x6b4e30 parse_block_data
        ../../gcc/fortran/parse.c:6026
0x6b4e30 gfc_parse_file()
        ../../gcc/fortran/parse.c:6413
0x70098f gfc_be_parse_file
        ../../gcc/fortran/f95-lang.c:212

             reply	other threads:[~2020-06-24 18:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24 18:52 gscfq@t-online.de [this message]
2020-06-24 21:10 ` [Bug fortran/95880] " dominiq at lps dot ens.fr
2020-06-25  2:19 ` kargl at gcc dot gnu.org
2020-06-25  7:09 ` [Bug fortran/95880] [9/10/11 Regression] ICE in gfc_add_type, at fortran/symbol.c:2030 since r11-524-geb069ae8819c3a84 marxin at gcc dot gnu.org
2020-06-25  7:35 ` rguenth at gcc dot gnu.org
2020-06-27 21:12 ` anlauf at gcc dot gnu.org
2020-06-27 21:28 ` anlauf at gcc dot gnu.org
2020-06-28 11:53 ` cvs-commit at gcc dot gnu.org
2020-06-29 15:47 ` cvs-commit at gcc dot gnu.org
2020-06-29 15:51 ` [Bug fortran/95880] [9 " anlauf at gcc dot gnu.org
2020-07-01 19:50 ` cvs-commit at gcc dot gnu.org
2020-07-01 19:54 ` 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-95880-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).