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/107995] New: ICE: Segmentation fault, without backtrace Date: Tue, 06 Dec 2022 18:06:07 +0000 [thread overview] Message-ID: <bug-107995-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107995 Bug ID: 107995 Summary: ICE: Segmentation fault, without backtrace Product: gcc Version: 13.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 : $ cat z1.f90 program p implicit none integer :: n n(n) = 1 print *, n(n) end $ cat z2.f90 program p n(n) = 1 print *, n(n) end $ gfortran-13-20221204 -c z1.f90 z1.f90:3:15: 3 | integer :: n | 1 Error: Self-referential argument 'n' at (1) is not allowed z1.f90:5:14: 5 | print *, n(n) | 1 Error: Statement function 'n' at (1) is not allowed as an actual argument gfortran: internal compiler error: Segmentation fault signal terminated program f951 Please submit a full bug report, with preprocessed source (by using -freport-bug). See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2022-12-06 18:06 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-06 18:06 gscfq@t-online.de [this message] 2022-12-10 2:19 ` [Bug fortran/107995] " kargl at gcc dot gnu.org 2022-12-10 19:37 ` anlauf at gcc dot gnu.org 2022-12-10 21:05 ` sgk at troutmask dot apl.washington.edu 2022-12-10 21:24 ` anlauf at gcc dot gnu.org 2022-12-11 19:35 ` cvs-commit at gcc dot gnu.org 2022-12-12 20:23 ` anlauf at gcc dot gnu.org 2022-12-12 21:43 ` sgk at troutmask dot apl.washington.edu 2022-12-12 21:49 ` 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-107995-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).