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/104573] New: ICE in resolve_structure_cons, at fortran/resolve.cc:1299
Date: Wed, 16 Feb 2022 17:35:46 +0000	[thread overview]
Message-ID: <bug-104573-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104573
           Summary: ICE in resolve_structure_cons, at
                    fortran/resolve.cc:1299
           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 :
(gcc configured with --enable-checking=yes)


$ cat z1.f90
program p
   type t
   end type
   type(*), parameter :: x = t()
   print *, x
end


$ cat z2.f90
program p
   type t
      integer :: n
   end type
   type(*), parameter :: x = t(1)
   print *, x
end


$ gfortran-12-20220213 -c z1.f90
z1.f90:4:26:

    4 |    type(*), parameter :: x = t()
      |                          1
Error: Assumed type of variable x at (1) is only permitted for dummy variables
z1.f90:4:28:

    4 |    type(*), parameter :: x = t()
      |                            1
Error: Cannot convert TYPE(t) to TYPE(*) at (1)
f951: internal compiler error: Segmentation fault
0xe7073f crash_signal
        ../../gcc/toplev.cc:322
0x7b30e4 resolve_structure_cons
        ../../gcc/fortran/resolve.cc:1299
0x7a0c91 gfc_resolve_expr(gfc_expr*)
        ../../gcc/fortran/resolve.cc:7228
0x7a9324 gfc_resolve_expr(gfc_expr*)
        ../../gcc/fortran/resolve.cc:7136
0x7a9324 gfc_resolve_code(gfc_code*, gfc_namespace*)
        ../../gcc/fortran/resolve.cc:11927
0x7a7cdf gfc_resolve_blocks(gfc_code*, gfc_namespace*)
        ../../gcc/fortran/resolve.cc:10943
0x7a8038 gfc_resolve_code(gfc_code*, gfc_namespace*)
        ../../gcc/fortran/resolve.cc:11917
0x7aa977 resolve_codes
        ../../gcc/fortran/resolve.cc:17536
0x7aaa3e gfc_resolve(gfc_namespace*)
        ../../gcc/fortran/resolve.cc:17571
0x792d64 resolve_all_program_units
        ../../gcc/fortran/parse.cc:6586
0x792d64 gfc_parse_file()
        ../../gcc/fortran/parse.cc:6842
0x7e102f gfc_be_parse_file
        ../../gcc/fortran/f95-lang.cc:216

             reply	other threads:[~2022-02-16 17:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 17:35 gscfq@t-online.de [this message]
2022-02-16 20:00 ` [Bug fortran/104573] " kargl at gcc dot gnu.org
2022-02-16 20:10 ` anlauf at gcc dot gnu.org
2022-02-16 20:25 ` sgk at troutmask dot apl.washington.edu
2022-02-16 20:32 ` anlauf at gcc dot gnu.org
2022-02-16 20:39 ` sgk at troutmask dot apl.washington.edu
2022-02-16 20:59 ` anlauf at gcc dot gnu.org
2022-02-16 21:20 ` anlauf at gcc dot gnu.org
2022-03-02 18:23 ` cvs-commit at gcc dot gnu.org
2022-03-02 18:25 ` 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-104573-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).