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/103610] ICE in gfc_convert_mpz_to_signed, at fortran/simplify.c:193
Date: Tue, 07 Dec 2021 19:46:16 +0000	[thread overview]
Message-ID: <bug-103610-4-qSvlOPtWkT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103610-4@http.gcc.gnu.org/bugzilla/>

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

G. Steinmetz <gscfq@t-online.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-invalid-code

--- Comment #1 from G. Steinmetz <gscfq@t-online.de> ---

$ cat z3.f90
program p
   integer, parameter :: a(-1) = 1
   integer, parameter :: b(1) = maskr(shape(a))
end


$ cat z4.f90
program p
   integer, parameter :: a(-1) = maskr(shape(a))
end


$ gfortran-12-20211205 -c z3.f90
gmp: overflow in mpz type
f951: internal compiler error: Aborted
0xf0b99f crash_signal
        ../../gcc/toplev.c:322
0x870a74 gfc_simplify_maskr(gfc_expr*, gfc_expr*)
        ../../gcc/fortran/simplify.c:4885
0x7ef826 do_simplify
        ../../gcc/fortran/intrinsic.c:4648
0x7fa888 gfc_intrinsic_func_interface(gfc_expr*, int)
        ../../gcc/fortran/intrinsic.c:4920
0x7e0359 gfc_simplify_expr(gfc_expr*, int)
        ../../gcc/fortran/expr.c:2219
0x7e0eaa scalarize_intrinsic_call
        ../../gcc/fortran/expr.c:2486
0x7e03ad gfc_simplify_expr(gfc_expr*, int)
        ../../gcc/fortran/expr.c:2227
0x7faa3e gfc_intrinsic_func_interface(gfc_expr*, int)
        ../../gcc/fortran/intrinsic.c:5070
0x84e86c resolve_unknown_f
        ../../gcc/fortran/resolve.c:2972
0x84e86c resolve_function
        ../../gcc/fortran/resolve.c:3329
0x84e86c gfc_resolve_expr(gfc_expr*)
        ../../gcc/fortran/resolve.c:7166
0x7df8a4 gfc_reduce_init_expr(gfc_expr*)
        ../../gcc/fortran/expr.c:3155
0x7e2810 gfc_match_init_expr(gfc_expr**)
        ../../gcc/fortran/expr.c:3203
0x7ccac4 variable_decl
        ../../gcc/fortran/decl.c:3004
0x7ccac4 gfc_match_data_decl()
        ../../gcc/fortran/decl.c:6297
0x836f03 match_word
        ../../gcc/fortran/parse.c:67
0x836f03 decode_statement
        ../../gcc/fortran/parse.c:378
0x83894a next_free
        ../../gcc/fortran/parse.c:1397
0x83894a next_statement
        ../../gcc/fortran/parse.c:1629
0x839edb parse_spec
        ../../gcc/fortran/parse.c:4168

  reply	other threads:[~2021-12-07 19:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 19:45 [Bug fortran/103610] New: " gscfq@t-online.de
2021-12-07 19:46 ` gscfq@t-online.de [this message]
2021-12-07 21:00 ` [Bug fortran/103610] " anlauf at gcc dot gnu.org
2021-12-07 21:39 ` anlauf at gcc dot gnu.org
2021-12-07 22:22 ` anlauf at gcc dot gnu.org
2021-12-08 18:35 ` cvs-commit at gcc dot gnu.org
2021-12-10 20:28 ` cvs-commit at gcc dot gnu.org
2021-12-17 21:48 ` cvs-commit at gcc dot gnu.org
2021-12-17 21:50 ` anlauf at gcc dot gnu.org
2021-12-17 21:53 ` cvs-commit at gcc dot gnu.org
2021-12-17 21:56 ` 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-103610-4-qSvlOPtWkT@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).