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/104848] New: ICE in simplify_intrinsic_op, at fortran/expr.cc:1305
Date: Tue, 08 Mar 2022 20:00:02 +0000	[thread overview]
Message-ID: <bug-104848-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104848
           Summary: ICE in simplify_intrinsic_op, at fortran/expr.cc:1305
           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: ---

Started with r8 :


$ cat z1.f90
program p
   integer, parameter :: a(2, 0) = 0
   integer, parameter :: b(0) = 1 + minval(a, dim=2)
end


$ cat z2.f90
program p
   integer, parameter :: a(2, 0) = 0
   integer, parameter :: b(1) = 1 + minval(a, dim=2)
end


$ cat z3.f90
program p
   integer, parameter :: a(2, 0) = 0
   integer, parameter :: b(2) = 1 + minval(a, dim=2)
end


$ gfortran-12-20220306 -c z1.f90
*** Error in `.../gcc/x86_64-pc-linux-gnu/12.0.1/f951': double free or
corruption (!prev): 0x0000000002da1030 ***
f951: internal compiler error: Aborted
0xccad7f crash_signal
        ../../gcc/toplev.cc:322
0x6f5cf2 simplify_intrinsic_op
        ../../gcc/fortran/expr.cc:1305
0x6f5cf2 gfc_simplify_expr(gfc_expr*, int)
        ../../gcc/fortran/expr.cc:2279
0x765c59 resolve_operator
        ../../gcc/fortran/resolve.cc:4499
0x761fef gfc_resolve_expr(gfc_expr*)
        ../../gcc/fortran/resolve.cc:7168
0x6f5044 gfc_reduce_init_expr(gfc_expr*)
        ../../gcc/fortran/expr.cc:3161
0x6f7fd0 gfc_match_init_expr(gfc_expr**)
        ../../gcc/fortran/expr.cc:3209
0x6e2354 variable_decl
        ../../gcc/fortran/decl.cc:3004
0x6e2354 gfc_match_data_decl()
        ../../gcc/fortran/decl.cc:6299
0x74cba3 match_word
        ../../gcc/fortran/parse.cc:67
0x74cba3 decode_statement
        ../../gcc/fortran/parse.cc:378
0x74e5ea next_free
        ../../gcc/fortran/parse.cc:1397
0x74e5ea next_statement
        ../../gcc/fortran/parse.cc:1629
0x74fb7b parse_spec
        ../../gcc/fortran/parse.cc:4168
0x752ccc parse_progunit
        ../../gcc/fortran/parse.cc:6192
0x754391 gfc_parse_file()
        ../../gcc/fortran/parse.cc:6737
0x7a1edf gfc_be_parse_file
        ../../gcc/fortran/f95-lang.cc:216

             reply	other threads:[~2022-03-08 20:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 20:00 gscfq@t-online.de [this message]
2022-03-09 19:34 ` [Bug fortran/104848] " anlauf at gcc dot gnu.org
2022-03-09 19:36 ` anlauf at gcc dot gnu.org
2022-03-09 19:54 ` anlauf at gcc dot gnu.org
2022-03-09 20:17 ` anlauf at gcc dot gnu.org
2022-10-19 19:18 ` anlauf at gcc dot gnu.org
2024-03-22 21:26 ` anlauf at gcc dot gnu.org
2024-03-22 21:30 ` anlauf at gcc dot gnu.org
2024-04-02 17:49 ` 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-104848-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).