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/103607] New: [9/10/11/12 Regression] ICE in do_subscript, at fortran/frontend-passes.c:2927 Date: Tue, 07 Dec 2021 19:41:40 +0000 [thread overview] Message-ID: <bug-103607-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103607 Bug ID: 103607 Summary: [9/10/11/12 Regression] ICE in do_subscript, at fortran/frontend-passes.c:2927 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, before 20180525 : (gcc configured with --enable-checking=yes) $ cat z1.f90 program p integer :: i, x(abs(2.)) do i = 1, 2 x(i) = 0 end do end $ gfortran-12-20211205 -c z1.f90 z1.f90:2:19: 2 | integer :: i, x(abs(2.)) | 1 Error: Expression at (1) must be of INTEGER type, found REAL z1.f90:2:27: 2 | integer :: i, x(abs(2.)) | 1 Error: The module or main program array 'x' at (1) must have constant shape f951: internal compiler error: Segmentation fault 0xf0b99f crash_signal ../../gcc/toplev.c:322 0x956154 do_subscript ../../gcc/fortran/frontend-passes.c:2927 0x956154 do_function ../../gcc/fortran/frontend-passes.c:2706 0x952495 gfc_expr_walker(gfc_expr**, int (*)(gfc_expr**, int*, void*), void*) ../../gcc/fortran/frontend-passes.c:5223 0x954601 gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int (*)(gfc_expr**, int*, void*), void*) ../../gcc/fortran/frontend-passes.c:5661 0x954697 gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int (*)(gfc_expr**, int*, void*), void*) ../../gcc/fortran/frontend-passes.c:5669 0x95570b doloop_warn ../../gcc/fortran/frontend-passes.c:3059 0x955c5a gfc_run_passes(gfc_namespace*) ../../gcc/fortran/frontend-passes.c:156 0x856467 gfc_resolve(gfc_namespace*) ../../gcc/fortran/resolve.c:17572 0x83e764 resolve_all_program_units ../../gcc/fortran/parse.c:6586 0x83e764 gfc_parse_file() ../../gcc/fortran/parse.c:6842 0x88c73f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:216
next reply other threads:[~2021-12-07 19:41 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-07 19:41 gscfq@t-online.de [this message] 2021-12-07 20:47 ` [Bug fortran/103607] " anlauf at gcc dot gnu.org 2021-12-07 22:18 ` cvs-commit at gcc dot gnu.org 2021-12-08 7:51 ` pinskia at gcc dot gnu.org 2021-12-08 9:04 ` marxin at gcc dot gnu.org 2021-12-08 19:18 ` cvs-commit at gcc dot gnu.org 2021-12-10 18:27 ` cvs-commit at gcc dot gnu.org 2021-12-10 18:32 ` cvs-commit at gcc dot gnu.org 2021-12-10 20:20 ` 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-103607-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).