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/87127] External function not recognised from within an associate block
Date: Mon, 20 Mar 2023 06:23:43 +0000 [thread overview]
Message-ID: <bug-87127-4-RFj9G0sUzz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-87127-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87127
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Paul Thomas <pault@gcc.gnu.org>:
https://gcc.gnu.org/g:9ccf471f8cc7341984f6613247f01d8ecfcb7ad5
commit r12-9295-g9ccf471f8cc7341984f6613247f01d8ecfcb7ad5
Author: Paul Thomas <pault@gcc.gnu.org>
Date: Mon Mar 20 06:23:29 2023 +0000
Fortran: Allow external function from in an associate block [PR87127]
2023-03-20 Paul Thomas <pault@gcc.gnu.org>
gcc/fortran
PR fortran/87127
* resolve.cc (check_host_association): If an external function
is typed but not declared explicitly to be external, change the
old symbol from a variable to an external function.
gcc/testsuite/
PR fortran/87127
* gfortran.dg/external_procedures_4.f90: New test.
next prev parent reply other threads:[~2023-03-20 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-87127-4@http.gcc.gnu.org/bugzilla/>
2021-03-01 17:06 ` vladimir.fuka at gmail dot com
2021-03-01 17:58 ` vladimir.fuka at gmail dot com
2023-03-20 6:14 ` cvs-commit at gcc dot gnu.org
2023-03-20 6:23 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-01 13:52 ` pault 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-87127-4-RFj9G0sUzz@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).