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/106987] New: [10/11/12/13 Regression] ICE in simplify_intrinsic_op, at fortran/expr.cc:1305
Date: Tue, 20 Sep 2022 17:37:48 +0000	[thread overview]
Message-ID: <bug-106987-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106987
           Summary: [10/11/12/13 Regression] ICE in simplify_intrinsic_op,
                    at fortran/expr.cc:1305
           Product: gcc
           Version: 13.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 r6 :


$ cat z1.f90
program p
!  integer, parameter :: a(1) = 31
   integer, parameter :: b(1) = 32
   integer, parameter :: c(1) = 33
!  print *, 2**a
   print *, 2**b
   print *, 2**c
end


$ gfortran-13-20220918 -c z1.f90
z1.f90:6:13:

    6 |    print *, 2**b
      |             1
Error: Arithmetic overflow at (1)
*** Error in `.../lib/gcc/x86_64-pc-linux-gnu/13.0.0/f951': free(): invalid
pointer: 0x0000000004260358 ***
f951: internal compiler error: Aborted
0xf3a72f crash_signal
        ../../gcc/toplev.cc:314
0x7f9af2 simplify_intrinsic_op
        ../../gcc/fortran/expr.cc:1305
0x7f9af2 gfc_simplify_expr(gfc_expr*, int)
        ../../gcc/fortran/expr.cc:2281
0x86ac39 resolve_operator
        ../../gcc/fortran/resolve.cc:4511
0x866fcf gfc_resolve_expr(gfc_expr*)
        ../../gcc/fortran/resolve.cc:7187
0x86f8bc gfc_resolve_expr(gfc_expr*)
        ../../gcc/fortran/resolve.cc:7161
0x86f8bc gfc_resolve_code(gfc_code*, gfc_namespace*)
        ../../gcc/fortran/resolve.cc:11974
0x86e34f gfc_resolve_blocks(gfc_code*, gfc_namespace*)
        ../../gcc/fortran/resolve.cc:10972
0x86e6a8 gfc_resolve_code(gfc_code*, gfc_namespace*)
        ../../gcc/fortran/resolve.cc:11964
0x871457 resolve_codes
        ../../gcc/fortran/resolve.cc:17617
0x87151e gfc_resolve(gfc_namespace*)
        ../../gcc/fortran/resolve.cc:17652
0x8592e4 resolve_all_program_units
        ../../gcc/fortran/parse.cc:6606
0x8592e4 gfc_parse_file()
        ../../gcc/fortran/parse.cc:6862
0x8a7ccf gfc_be_parse_file
        ../../gcc/fortran/f95-lang.cc:229

             reply	other threads:[~2022-09-20 17:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 17:37 gscfq@t-online.de [this message]
2022-09-20 17:38 ` [Bug fortran/106987] " gscfq@t-online.de
2022-09-20 18:54 ` anlauf at gcc dot gnu.org
2022-09-21  7:50 ` rguenth at gcc dot gnu.org
2023-07-07 10:44 ` [Bug fortran/106987] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-06 16:57 ` cvs-commit at gcc dot gnu.org
2024-03-31 12:19 ` pault at gcc dot gnu.org
2024-04-01 20:42 ` anlauf at gcc dot gnu.org
2024-04-02 13:32 ` paul.richard.thomas at gmail dot com
2024-04-02 14:40 ` paul.richard.thomas at gmail dot com
2024-04-02 17:07 ` cvs-commit at gcc dot gnu.org
2024-04-02 17:38 ` 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-106987-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).