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/104211] New: ICE in find_array_section, at fortran/expr.cc:1720
Date: Mon, 24 Jan 2022 19:00:38 +0000	[thread overview]
Message-ID: <bug-104211-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104211
           Summary: ICE in find_array_section, at fortran/expr.cc:1720
           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 :


$ cat z1.f90
program p
   type t
      real :: n
   end type
   type(t), parameter :: a(3) = [t(2)]
   type(t), parameter :: b(2) = a(2:3)
end


$ cat z2.f90
program p
   type t
      real :: n
   end type
   type(t), parameter :: a(3) = [t(2)]
   type(t), parameter :: b(2) = [a(2:3)]
end


$ gfortran-12-20220123 -c z1.f90
f951: internal compiler error: in find_array_section, at fortran/expr.cc:1720
0x6f0d75 find_array_section
        ../../gcc/fortran/expr.cc:1720
0x6f231a simplify_const_ref
        ../../gcc/fortran/expr.cc:1925
0x6f2e4e gfc_simplify_expr(gfc_expr*, int)
        ../../gcc/fortran/expr.cc:2316
0x6f30bb simplify_parameter_variable
        ../../gcc/fortran/expr.cc:2145
0x6f2007 gfc_reduce_init_expr(gfc_expr*)
        ../../gcc/fortran/expr.cc:3156
0x6f4f70 gfc_match_init_expr(gfc_expr**)
        ../../gcc/fortran/expr.cc:3202
0x6df324 variable_decl
        ../../gcc/fortran/decl.cc:3004
0x6df324 gfc_match_data_decl()
        ../../gcc/fortran/decl.cc:6299
0x749933 match_word
        ../../gcc/fortran/parse.cc:67
0x749933 decode_statement
        ../../gcc/fortran/parse.cc:378
0x74b37a next_free
        ../../gcc/fortran/parse.cc:1397
0x74b37a next_statement
        ../../gcc/fortran/parse.cc:1629
0x74c90b parse_spec
        ../../gcc/fortran/parse.cc:4168
0x74fa5c parse_progunit
        ../../gcc/fortran/parse.cc:6192
0x751121 gfc_parse_file()
        ../../gcc/fortran/parse.cc:6737
0x79e86f gfc_be_parse_file
        ../../gcc/fortran/f95-lang.cc:216

             reply	other threads:[~2022-01-24 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 19:00 gscfq@t-online.de [this message]
2022-01-24 20:01 ` [Bug fortran/104211] " anlauf at gcc dot gnu.org
2022-02-10 20:29 ` anlauf at gcc dot gnu.org
2022-02-14 20:07 ` cvs-commit at gcc dot gnu.org
2022-02-16 21:35 ` cvs-commit at gcc dot gnu.org
2022-02-16 21:37 ` 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-104211-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).