public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vterzi1996 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/108921] New: ICE: using the result of an impure function in automatic character allocation Date: Fri, 24 Feb 2023 10:43:26 +0000 [thread overview] Message-ID: <bug-108921-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108921 Bug ID: 108921 Summary: ICE: using the result of an impure function in automatic character allocation Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: vterzi1996 at gmail dot com Target Milestone: --- Created attachment 54527 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54527&action=edit Complete backtrace Consider the following minimal working example: ``` module lib type t contains procedure::f,g end type contains integer function f(this) class(t),intent(in)::this f=10 end function g(this)result(r) class(t),intent(in)::this character(len=this%f())::r ! problem appears here r='42' end end program prog use lib type(t)::o print*,o%g() end ``` This example was already discussed here: https://stackoverflow.com/questions/75544072/using-function-result-as-character-length-in-fortran The compilation of this code with the GNU compiler (gfortran 12.2.0 on Rocky Linux 8.7) fails with the message `f951: internal compiler error: Segmentation fault` (full output is in the attachment). It also fails with 7.5.0, 9.4.0, and 11.1.0 on Ubuntu 18.04.2 LTS. The reason for this problem is the unallowed usage of the result of an impure function (here: `f`) in the automatic allocation of the CHARACTER variable, but the compiler fails to identify the mistake in the code.
next reply other threads:[~2023-02-24 10:43 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-24 10:43 vterzi1996 at gmail dot com [this message] 2023-02-24 17:36 ` [Bug fortran/108921] " kargl 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-108921-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).