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/103505] New: ICE in compare_bound_mpz_t, at fortran/resolve.c:4587 Date: Tue, 30 Nov 2021 18:47:19 +0000 [thread overview] Message-ID: <bug-103505-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103505 Bug ID: 103505 Summary: ICE in compare_bound_mpz_t, at fortran/resolve.c:4587 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.)) = [4, 8] integer(a(1:1)) :: b end $ cat z2.f90 program p integer, parameter :: a((2.)) = [4, 8] print *, [integer(a(1:1)) :: 2] end $ cat z3.f90 program p integer, parameter :: a((2.)) = [4, 8] integer :: b(a(1:1)) end $ gfortran-12-20211128 -c z1.f90 f951: internal compiler error: compare_bound_int(): Bad expression 0x7977b9 gfc_report_diagnostic ../../gcc/fortran/error.c:874 0x799327 gfc_internal_error(char const*, ...) ../../gcc/fortran/error.c:1494 0x807111 compare_bound_mpz_t ../../gcc/fortran/resolve.c:4587 0x80765c check_dimension ../../gcc/fortran/resolve.c:4770 0x81a51d compare_spec_to_ref ../../gcc/fortran/resolve.c:4835 0x81a51d resolve_array_ref ../../gcc/fortran/resolve.c:5126 0x81a51d gfc_resolve_ref(gfc_expr*) ../../gcc/fortran/resolve.c:5340 0x80a7a7 resolve_variable ../../gcc/fortran/resolve.c:5842 0x80a7a7 gfc_resolve_expr(gfc_expr*) ../../gcc/fortran/resolve.c:7168 0x79d694 gfc_reduce_init_expr(gfc_expr*) ../../gcc/fortran/expr.c:3130 0x7a0560 gfc_match_init_expr(gfc_expr**) ../../gcc/fortran/expr.c:3178 0x781265 gfc_match_kind_spec(gfc_typespec*, bool) ../../gcc/fortran/decl.c:3241 0x787ae9 gfc_match_decl_type_spec(gfc_typespec*, int) ../../gcc/fortran/decl.c:4672 0x78947c gfc_match_data_decl() ../../gcc/fortran/decl.c:6226 0x7f49c3 match_word ../../gcc/fortran/parse.c:67 0x7f49c3 decode_statement ../../gcc/fortran/parse.c:378 0x7f640a next_free ../../gcc/fortran/parse.c:1397 0x7f640a next_statement ../../gcc/fortran/parse.c:1629 0x7f7b2b parse_spec ../../gcc/fortran/parse.c:4168 0x7fae8c parse_progunit ../../gcc/fortran/parse.c:6179
next reply other threads:[~2021-11-30 18:47 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-30 18:47 gscfq@t-online.de [this message] 2021-11-30 20:44 ` [Bug fortran/103505] " anlauf at gcc dot gnu.org 2021-11-30 20:48 ` kargl at gcc dot gnu.org 2021-12-01 9:25 ` [Bug fortran/103505] ICE in compare_bound_mpz_t, at fortran/resolve.c:4587 since r8-7594-g078c5aff5ed83e9c marxin at gcc dot gnu.org 2021-12-01 20:26 ` anlauf at gcc dot gnu.org 2021-12-01 21:00 ` sgk at troutmask dot apl.washington.edu 2021-12-01 21:42 ` anlauf at gcc dot gnu.org 2021-12-01 22:29 ` sgk at troutmask dot apl.washington.edu 2021-12-02 21:51 ` anlauf at gcc dot gnu.org 2021-12-03 20:08 ` cvs-commit at gcc dot gnu.org 2021-12-03 20:26 ` sgk at troutmask dot apl.washington.edu 2021-12-03 21:24 ` anlauf at gcc dot gnu.org 2021-12-04 21:31 ` cvs-commit at gcc dot gnu.org 2021-12-19 20:29 ` cvs-commit at gcc dot gnu.org 2021-12-19 21:00 ` [Bug fortran/103505] [9 Regression] " anlauf at gcc dot gnu.org 2022-01-17 9:01 ` rguenth at gcc dot gnu.org 2022-05-27 9:51 ` rguenth 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-103505-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: linkBe 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).