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/108528] New: [13 Regression] ICE in gfc_compare_array_spec(): Array spec clobbered Date: Tue, 24 Jan 2023 17:52:10 +0000 [thread overview] Message-ID: <bug-108528-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108528 Bug ID: 108528 Summary: [13 Regression] ICE in gfc_compare_array_spec(): Array spec clobbered 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 between 20221218 and 20230108 : $ cat z1.f90 function f() integer :: f((2.)) integer :: g((2)) entry g() end $ cat z2.f90 function f() integer :: f(real(2)) integer :: g((2)) entry g() end $ gfortran-13-20230122 -c z1.f90 f951: internal compiler error: gfc_compare_array_spec(): Array spec clobbered 0x7c17e9 gfc_report_diagnostic ../../gcc/fortran/error.cc:883 0x7c3387 gfc_internal_error(char const*, ...) ../../gcc/fortran/error.cc:1503 0x78dda4 compare_bounds ../../gcc/fortran/array.cc:982 0x78f73c gfc_compare_array_spec(gfc_array_spec*, gfc_array_spec*) ../../gcc/fortran/array.cc:1026 0x8333ff resolve_entries ../../gcc/fortran/resolve.cc:799 0x8461ef resolve_types ../../gcc/fortran/resolve.cc:17531 0x84175c gfc_resolve(gfc_namespace*) ../../gcc/fortran/resolve.cc:17662 0x8294d4 resolve_all_program_units ../../gcc/fortran/parse.cc:6656 0x8294d4 gfc_parse_file() ../../gcc/fortran/parse.cc:6912 0x8774bf gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:229
next reply other threads:[~2023-01-24 17:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-24 17:52 gscfq@t-online.de [this message] 2023-01-24 19:08 ` [Bug fortran/108528] " kargl at gcc dot gnu.org 2023-01-24 19:08 ` kargl at gcc dot gnu.org 2023-01-24 20:25 ` anlauf at gcc dot gnu.org 2023-01-25 7:36 ` rguenth at gcc dot gnu.org 2023-01-25 19:44 ` anlauf at gcc dot gnu.org 2023-01-25 19:47 ` cvs-commit at gcc dot gnu.org 2023-01-25 19:52 ` sgk at troutmask dot apl.washington.edu 2023-01-25 19:54 ` 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-108528-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).