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/102331] New: ICE in attr_decl1, at fortran/decl.c:8691
Date: Tue, 14 Sep 2021 17:29:07 +0000	[thread overview]
Message-ID: <bug-102331-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102331
           Summary: ICE in attr_decl1, at fortran/decl.c:8691
           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 at least r5 (type t not defined) :


$ cat z1.f90
class(t) function f()
   allocatable :: f
end


$ cat z2.f90
class(t) function f()
   pointer :: f
end


$ gfortran-12-20210905 -c z1.f90
f951: internal compiler error: Segmentation fault
0xeace0f crash_signal
        ../../gcc/toplev.c:328
0x7882b4 attr_decl1
        ../../gcc/fortran/decl.c:8691
0x7882b4 attr_decl
        ../../gcc/fortran/decl.c:8777
0x7f7db1 match_word
        ../../gcc/fortran/parse.c:65
0x7fd189 decode_statement
        ../../gcc/fortran/parse.c:441
0x7fda8a next_free
        ../../gcc/fortran/parse.c:1384
0x7fda8a next_statement
        ../../gcc/fortran/parse.c:1616
0x7ff2ad parse_spec
        ../../gcc/fortran/parse.c:4164
0x801f9c parse_progunit
        ../../gcc/fortran/parse.c:6114
0x803a37 gfc_parse_file()
        ../../gcc/fortran/parse.c:6669
0x8510ff gfc_be_parse_file
        ../../gcc/fortran/f95-lang.c:216

             reply	other threads:[~2021-09-14 17:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 17:29 gscfq@t-online.de [this message]
2021-09-14 17:29 ` [Bug fortran/102331] " gscfq@t-online.de
2021-09-15  8:51 ` marxin at gcc dot gnu.org
2021-09-15 17:20 ` kargl at gcc dot gnu.org
2021-09-15 20:57 ` anlauf at gcc dot gnu.org
2021-09-15 21:59 ` sgk at troutmask dot apl.washington.edu
2022-12-26 19:55 ` jvdelisle at gcc dot gnu.org
2022-12-26 20:14 ` jvdelisle at gcc dot gnu.org
2023-01-14  3:29 ` jvdelisle at gcc dot gnu.org
2023-01-18  1:37 ` jvdelisle at gcc dot gnu.org
2023-03-27  2:00 ` cvs-commit at gcc dot gnu.org
2023-05-29 22:06 ` kargl 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-102331-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).