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/104351] New: ICE in gfc_generate_initializer, at fortran/expr.cc:5140 Date: Wed, 02 Feb 2022 18:45:25 +0000 [thread overview] Message-ID: <bug-104351-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104351 Bug ID: 104351 Summary: ICE in gfc_generate_initializer, at fortran/expr.cc:5140 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 : (name conflict) $ cat z1.f90 program p implicit none type t end type type(t) :: f contains real function f() result(z) z = 0.0 end end $ gfortran-12-20220130 -c z1.f90 z1.f90:9:6: 9 | end | 1 internal compiler error: Segmentation fault 0xcc655f crash_signal ../../gcc/toplev.cc:322 0x6f484a gfc_generate_initializer(gfc_typespec*, bool) ../../gcc/fortran/expr.cc:5140 0x7d05b7 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.cc:7709 0x7cefcc gfc_generate_contained_functions ../../gcc/fortran/trans-decl.cc:5777 0x7cefcc gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.cc:7586 0x751efe translate_all_program_units ../../gcc/fortran/parse.cc:6651 0x751efe gfc_parse_file() ../../gcc/fortran/parse.cc:6938 0x79eecf gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:216
next reply other threads:[~2022-02-02 18:45 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-02 18:45 gscfq@t-online.de [this message] 2022-02-02 18:45 ` [Bug fortran/104351] " gscfq@t-online.de 2023-10-10 21:02 ` anlauf at gcc dot gnu.org 2023-10-11 19:41 ` anlauf at gcc dot gnu.org 2023-10-13 20:08 ` cvs-commit at gcc dot gnu.org 2023-10-14 20:02 ` 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-104351-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).