public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "shepard at tcg dot anl.gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/106606] New: Internal compiler error with abstract derived type using recursive class() components. Date: Sat, 13 Aug 2022 05:36:39 +0000 [thread overview] Message-ID: <bug-106606-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106606 Bug ID: 106606 Summary: Internal compiler error with abstract derived type using recursive class() components. Product: gcc Version: 11.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: shepard at tcg dot anl.gov Target Milestone: --- Created attachment 53449 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53449&action=edit This is a small file that demonstrates the error. $ gfortran error.F90 gfortran: internal compiler error: Segmentation fault: 11 signal terminated program f951 Please submit a full bug report, with preprocessed source if appropriate. See <https://github.com/Homebrew/homebrew-core/issues> for instructions. $ gfortran --version GNU Fortran (Homebrew GCC 11.3.0_2) 11.3.0 Copyright (C) 2021 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next reply other threads:[~2022-08-13 5:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-13 5:36 shepard at tcg dot anl.gov [this message] 2022-08-13 17:59 ` [Bug fortran/106606] " johaweb at hotmail dot com 2022-08-16 6:21 ` [Bug fortran/106606] Internal compiler error with abstract derived type using recursive class() components. since r7-4096-gbf9f15ee55f5b291 marxin 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-106606-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).