public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109846] [rejects valid] Pointer-valued function reference rejected as actual argument Date: Sat, 13 May 2023 21:58:54 +0000 [thread overview] Message-ID: <bug-109846-4-E1NOfkVCnK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109846-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109846 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P4 CC| |kargl at gcc dot gnu.org --- Comment #1 from kargl at gcc dot gnu.org --- Confirmed. Workaround seems to be to not use a RESULT variable. This change seems to work function sublist(this) class(parameter_list), intent(inout) :: this class(parameter_list), pointer :: sublist allocate(sublist) end function
next prev parent reply other threads:[~2023-05-13 21:58 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-13 20:42 [Bug fortran/109846] New: " neil.n.carlson at gmail dot com 2023-05-13 21:58 ` kargl at gcc dot gnu.org [this message] 2023-05-13 22:29 ` [Bug fortran/109846] " neil.n.carlson at gmail dot com 2023-05-14 19:15 ` [Bug fortran/109846] " anlauf at gcc dot gnu.org 2023-05-14 19:30 ` anlauf at gcc dot gnu.org 2023-05-14 20:05 ` anlauf at gcc dot gnu.org 2023-05-15 17:27 ` cvs-commit at gcc dot gnu.org 2023-05-18 16:54 ` cvs-commit at gcc dot gnu.org 2023-05-20 20:20 ` cvs-commit at gcc dot gnu.org 2023-05-20 20:37 ` cvs-commit at gcc dot gnu.org 2023-05-20 20:40 ` 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-109846-4-E1NOfkVCnK@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).