public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/110224] Rejects valid: function reference with data pointer result as lhs in assignment Date: Wed, 21 Jun 2023 21:05:02 +0000 [thread overview] Message-ID: <bug-110224-4-fTHmVCiBUG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110224-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110224 Paul Thomas <pault at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #11 from Paul Thomas <pault at gcc dot gnu.org> --- Fixed on trunk and closing. I will build a composite patch for 13-branch in a few weeks. Thanks for the report Paul PS I am going through your gfortran-bugs and find that a good number are fixed. However, there are some humdingers going back a long way that I will take a look at, once I am done with associate.
next prev parent reply other threads:[~2023-06-21 21:05 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-12 13:14 [Bug fortran/110224] New: " neil.n.carlson at gmail dot com 2023-06-13 16:49 ` [Bug fortran/110224] " anlauf at gcc dot gnu.org 2023-06-17 16:53 ` pault at gcc dot gnu.org 2023-06-20 9:48 ` pault at gcc dot gnu.org 2023-06-20 11:47 ` neil.n.carlson at gmail dot com 2023-06-20 11:53 ` neil.n.carlson at gmail dot com 2023-06-20 14:10 ` pault at gcc dot gnu.org 2023-06-20 14:42 ` neil.n.carlson at gmail dot com 2023-06-20 15:47 ` pault at gcc dot gnu.org 2023-06-20 16:36 ` neil.n.carlson at gmail dot com 2023-06-21 16:06 ` cvs-commit at gcc dot gnu.org 2023-06-21 21:05 ` pault at gcc dot gnu.org [this message] 2023-06-22 13:17 ` neil.n.carlson at gmail dot com
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-110224-4-fTHmVCiBUG@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).