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/104571] New: ICE in resolve_elemental_actual, at fortran/resolve.cc:2383 Date: Wed, 16 Feb 2022 17:33:53 +0000 [thread overview] Message-ID: <bug-104571-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104571 Bug ID: 104571 Summary: ICE in resolve_elemental_actual, at fortran/resolve.cc:2383 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: --- Affects versions down to at least r5 : (gcc configured with --enable-checking=yes) $ cat z1.f90 program p real :: x(3) call g(x) contains elemental subroutine g(*) end end $ gfortran-12-20220213 -c z1.f90 z1.f90:5:25: 5 | elemental subroutine g(*) | 1 Error: Alternate return specifier in elemental subroutine 'g' at (1) is not allowed z1.f90:3:12: 3 | call g(x) | 1 Error: Missing alternate return specifier in subroutine call at (1) f951: internal compiler error: Segmentation fault 0xe7073f crash_signal ../../gcc/toplev.cc:322 0x79bd73 resolve_elemental_actual ../../gcc/fortran/resolve.cc:2383 0x7ab0bb resolve_call ../../gcc/fortran/resolve.cc:3805 0x7a8449 gfc_resolve_code(gfc_code*, gfc_namespace*) ../../gcc/fortran/resolve.cc:12154 0x7aa977 resolve_codes ../../gcc/fortran/resolve.cc:17536 0x7aaa3e gfc_resolve(gfc_namespace*) ../../gcc/fortran/resolve.cc:17571 0x792d64 resolve_all_program_units ../../gcc/fortran/parse.cc:6586 0x792d64 gfc_parse_file() ../../gcc/fortran/parse.cc:6842 0x7e102f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:216
next reply other threads:[~2022-02-16 17:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-16 17:33 gscfq@t-online.de [this message] 2022-02-16 19:27 ` [Bug fortran/104571] " kargl at gcc dot gnu.org 2022-03-29 20:09 ` anlauf at gcc dot gnu.org 2022-03-29 20:12 ` cvs-commit at gcc dot gnu.org 2022-03-29 20:19 ` 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-104571-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).