public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/114739] New: [14 Regression] ice in gfc_find_derived_types, at fortran/symbol.cc:2458 Date: Tue, 16 Apr 2024 11:10:03 +0000 [thread overview] Message-ID: <bug-114739-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114739 Bug ID: 114739 Summary: [14 Regression] ice in gfc_find_derived_types, at fortran/symbol.cc:2458 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- From the flang testsuite at https://github.com/llvm/llvm-project/tree/main/flang/test file ./Semantics/symbol07.f90, does this with gfortran 13.2: $ ~/gcc/results.13.2.asan.ubsan/bin/gfortran -c -w ./Semantics/symbol07.f90 ./Semantics/symbol07.f90:28:5: 28 | z2%re = x | 1 Error: Symbol ‘z2’ at (1) has no IMPLICIT type ./Semantics/symbol07.f90:31:5: 31 | z2%im = y | 1 Error: Symbol ‘z2’ at (1) has no IMPLICIT type $ and this with yesterday's gfortran: $ ~/gcc/results.20240415.asan.ubsan/bin/gfortran -c -w ./Semantics/symbol07.f90 f951: internal compiler error: in gfc_find_derived_types, at fortran/symbol.cc:2458 0x6f3ca3 gfc_find_derived_types(gfc_symbol*, gfc_namespace*, char const*, bool) ../../trunk.20210101/gcc/fortran/symbol.cc:2458 0x9e1686 gfc_match_varspec(gfc_expr*, int, bool, bool) ../../trunk.20210101/gcc/fortran/primary.cc:2246 0x9e1916 match_variable ../../trunk.20210101/gcc/fortran/primary.cc:4309 0x99a364 gfc_match(char const*, ...) ../../trunk.20210101/gcc/fortran/match.cc:1144
next reply other threads:[~2024-04-16 11:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-16 11:10 dcb314 at hotmail dot com [this message] 2024-04-16 14:55 ` [Bug fortran/114739] " kargls at comcast dot net 2024-04-16 15:05 ` dcb314 at hotmail dot com 2024-04-16 16:55 ` anlauf at gcc dot gnu.org 2024-04-16 19:04 ` anlauf at gcc dot gnu.org 2024-04-16 19:27 ` anlauf at gcc dot gnu.org 2024-04-17 16:28 ` pault at gcc dot gnu.org 2024-04-18 17:07 ` cvs-commit at gcc dot gnu.org 2024-04-19 8:00 ` pault at gcc dot gnu.org 2024-04-19 15:45 ` pault at gcc dot gnu.org 2024-04-23 9:39 ` [Bug fortran/114739] Ensure no IMPLICIT type errors appear when they should for inquiry references pault at gcc dot gnu.org 2024-05-06 7:21 ` cvs-commit at gcc dot gnu.org 2024-05-06 7:45 ` cvs-commit at gcc dot gnu.org 2024-05-06 7:48 ` pault 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-114739-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).