public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97245] ASSOCIATED intrinsic does not recognize a pointer variable the second time it is used
Date: Sat, 04 Nov 2023 14:50:23 +0000 [thread overview]
Message-ID: <bug-97245-4-HO5DEqixyY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97245-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97245
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:e6ea74b68c5904446da6050751fde97d02549d1f
commit r13-8002-ge6ea74b68c5904446da6050751fde97d02549d1f
Author: Harald Anlauf <anlauf@gmx.de>
Date: Fri Nov 3 19:41:54 2023 +0100
Fortran: fix issue with multiple references of a procedure pointer
[PR97245]
gcc/fortran/ChangeLog:
PR fortran/97245
* match.cc (gfc_match_call): If a procedure pointer has already
been
resolved, do not create a new symbol in a procedure reference of
the same name shadowing the first one if it is host-associated.
gcc/testsuite/ChangeLog:
PR fortran/97245
* gfortran.dg/proc_ptr_53.f90: New test.
(cherry picked from commit 5340f48b7639fcc874f64aac214f9ef9ae43d43e)
next prev parent reply other threads:[~2023-11-04 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 16:23 [Bug fortran/97245] New: ASSOCIATE intrinsic does not recognize a ponter " aluaces at udc dot es
2020-10-02 13:52 ` [Bug fortran/97245] " dominiq at lps dot ens.fr
2023-11-02 21:46 ` [Bug fortran/97245] ASSOCIATED intrinsic does not recognize a pointer " anlauf at gcc dot gnu.org
2023-11-03 17:55 ` anlauf at gcc dot gnu.org
2023-11-03 18:57 ` anlauf at gcc dot gnu.org
2023-11-03 21:11 ` cvs-commit at gcc dot gnu.org
2023-11-04 14:50 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-04 14:53 ` 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-97245-4-HO5DEqixyY@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: link
Be 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).