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/107380] New: ICE in coarray_check, at fortran/check.cc:694 Date: Mon, 24 Oct 2022 17:51:09 +0000 [thread overview] Message-ID: <bug-107380-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107380 Bug ID: 107380 Summary: ICE in coarray_check, at fortran/check.cc:694 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: --- Affects versions down to at least r5 : $ cat z1.f90 program p class(*), allocatable :: x codimension :: x[:] allocate (real :: x[*]) print *, image_index(x, [1]) end $ cat z2.f90 program p class(*), allocatable :: x[:] allocate (real :: x[*]) print *, image_index(x, [1]) end $ gfortran-13-20221023 -c z2.f90 -fcoarray=lib $ $ gfortran-13-20221023 -c z1.f90 -fcoarray=lib z1.f90:4:24: 4 | allocate (real :: x[*]) | 1 Error: Unexpected coarray designator at (1) f951: internal compiler error: Segmentation fault 0xf43b3f crash_signal ../../gcc/toplev.cc:314 0x7ca22f coarray_check ../../gcc/fortran/check.cc:694 0x7d2482 gfc_check_image_index(gfc_expr*, gfc_expr*) ../../gcc/fortran/check.cc:5943 0x811b09 do_check ../../gcc/fortran/intrinsic.cc:4792 0x811b09 check_specific ../../gcc/fortran/intrinsic.cc:4805 0x819b94 gfc_intrinsic_func_interface(gfc_expr*, int) ../../gcc/fortran/intrinsic.cc:5042 0x870468 resolve_unknown_f ../../gcc/fortran/resolve.cc:2990 0x870468 resolve_function ../../gcc/fortran/resolve.cc:3347 0x870468 gfc_resolve_expr(gfc_expr*) ../../gcc/fortran/resolve.cc:7194 0x8766cc gfc_resolve_expr(gfc_expr*) ../../gcc/fortran/resolve.cc:7161 0x8766cc gfc_resolve_code(gfc_code*, gfc_namespace*) ../../gcc/fortran/resolve.cc:11980 0x8751ff gfc_resolve_blocks(gfc_code*, gfc_namespace*) ../../gcc/fortran/resolve.cc:10978 0x875558 gfc_resolve_code(gfc_code*, gfc_namespace*) ../../gcc/fortran/resolve.cc:11970 0x878307 resolve_codes ../../gcc/fortran/resolve.cc:17624 0x8783ce gfc_resolve(gfc_namespace*) ../../gcc/fortran/resolve.cc:17659 0x860194 resolve_all_program_units ../../gcc/fortran/parse.cc:6631 0x860194 gfc_parse_file() ../../gcc/fortran/parse.cc:6887 0x8aec0f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:229
next reply other threads:[~2022-10-24 17:51 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-24 17:51 gscfq@t-online.de [this message] 2022-10-24 19:20 ` [Bug fortran/107380] " anlauf at gcc dot gnu.org 2023-03-06 17:11 ` 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-107380-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).