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/98897] Erroneous procedure attribute for associate name
Date: Thu, 11 Feb 2021 19:10:09 +0000 [thread overview]
Message-ID: <bug-98897-4-FPiUfhAek4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98897-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98897
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Paul Thomas <pault@gcc.gnu.org>:
https://gcc.gnu.org/g:9d3b9a3e70e634c7c48bb12bb35ec8219024f98b
commit r10-9358-g9d3b9a3e70e634c7c48bb12bb35ec8219024f98b
Author: Paul Thomas <pault@gcc.gnu.org>
Date: Thu Feb 11 13:24:50 2021 +0000
Fortran: Fix calls to associate name typebound subroutines [PR98897].
2021-02-11 Paul Thomas <pault@gcc.gnu.org>
gcc/fortran
PR fortran/98897
* match.c (gfc_match_call): Include associate names as possible
entities with typebound subroutines. The target needs to be
resolved for the type.
gcc/testsuite/
PR fortran/98897
* gfortran.dg/typebound_call_32.f90: New test.
(cherry picked from commit ff6903288d96aa1d28ae4912b1270985475f3ba8)
next prev parent reply other threads:[~2021-02-11 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 0:13 [Bug fortran/98897] New: " damian at sourceryinstitute dot org
2021-02-01 8:56 ` [Bug fortran/98897] " burnus at gcc dot gnu.org
2021-02-02 12:05 ` pault at gcc dot gnu.org
2021-02-02 16:28 ` damian at sourceryinstitute dot org
2021-02-11 13:25 ` cvs-commit at gcc dot gnu.org
2021-02-11 19:10 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-11 19:11 ` pault at gcc dot gnu.org
2021-02-13 11:53 ` dominiq at lps dot ens.fr
2021-02-23 0:43 ` damian at sourceryinstitute dot 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-98897-4-FPiUfhAek4@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).