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/103471] New: [9/10/11/12 Regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1114 Date: Mon, 29 Nov 2021 18:48:06 +0000 [thread overview] Message-ID: <bug-103471-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103471 Bug ID: 103471 Summary: [9/10/11/12 Regression] ICE in gfc_typenode_for_spec, at fortran/trans-types.c:1114 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: --- Some time ago, r8 was corrected, between 20191115 (ICE) and 20200507 (error), but the ICE appeared again in r9 : (follow-up of pr93484) $ cat z1.f90 program p implicit none print *, [real(x(k))] end $ gfortran-8 -c z1.f90 z1.f90:3:21: print *, [real(x(k))] 1 Error: Symbol 'k' at (1) has no IMPLICIT type $ gfortran-12-20211128 -c z1.f90 z1.f90:1:9: 1 | program p | 1 internal compiler error: in gfc_typenode_for_spec, at fortran/trans-types.c:1114 0x8d8bb0 gfc_typenode_for_spec(gfc_typespec*, int) ../../gcc/fortran/trans-types.c:1114 0x8d8db6 gfc_sym_type(gfc_symbol*, bool) ../../gcc/fortran/trans-types.c:2272 0x875938 gfc_get_symbol_decl(gfc_symbol*) ../../gcc/fortran/trans-decl.c:1813 0x87830f generate_local_decl ../../gcc/fortran/trans-decl.c:5848 0x834652 do_traverse_symtree ../../gcc/fortran/symbol.c:4174 0x87944c generate_local_vars ../../gcc/fortran/trans-decl.c:6054 0x87944c gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.c:7579 0x7fc90e translate_all_program_units ../../gcc/fortran/parse.c:6638 0x7fc90e gfc_parse_file() ../../gcc/fortran/parse.c:6925 0x84967f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:216
next reply other threads:[~2021-11-29 18:48 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-29 18:48 gscfq@t-online.de [this message] 2021-11-30 7:03 ` [Bug fortran/103471] " rguenth at gcc dot gnu.org 2021-11-30 14:20 ` marxin at gcc dot gnu.org 2021-12-23 0:35 ` kargl at gcc dot gnu.org 2022-05-27 9:46 ` [Bug fortran/103471] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:47 ` jakub at gcc dot gnu.org 2023-07-07 10:41 ` [Bug fortran/103471] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-04-11 17:34 ` pault at gcc dot gnu.org 2024-04-18 20:38 ` anlauf at gcc dot gnu.org 2024-04-19 6:02 ` pault at gcc dot gnu.org 2024-04-19 6:02 ` pault at gcc dot gnu.org 2024-04-19 7:25 ` pault at gcc dot gnu.org 2024-04-21 16:24 ` cvs-commit at gcc dot gnu.org 2024-04-21 16:34 ` [Bug fortran/103471] Missed no IMPLICIT type errors 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-103471-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).