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/87477] [meta-bug] [F03] issues concerning the ASSOCIATE statement
Date: Wed, 21 Jun 2023 16:06:10 +0000 [thread overview]
Message-ID: <bug-87477-4-ja2ZsjiBXw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-87477-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87477
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>:
https://gcc.gnu.org/g:577223aebc7acdd31e62b33c1682fe54a622ae27
commit r14-2022-g577223aebc7acdd31e62b33c1682fe54a622ae27
Author: Paul Thomas <pault@gcc.gnu.org>
Date: Wed Jun 21 17:05:58 2023 +0100
Fortran: Fix some bugs in associate [PR87477]
2023-06-21 Paul Thomas <pault@gcc.gnu.org>
gcc/fortran
PR fortran/87477
PR fortran/88688
PR fortran/94380
PR fortran/107900
PR fortran/110224
* decl.cc (char_len_param_value): Fix memory leak.
(resolve_block_construct): Remove unnecessary static decls.
* expr.cc (gfc_is_ptr_fcn): New function.
(gfc_check_vardef_context): Use it to permit pointer function
result selectors to be used for associate names in variable
definition context.
* gfortran.h: Prototype for gfc_is_ptr_fcn.
* match.cc (build_associate_name): New function.
(gfc_match_select_type): Use the new function to replace inline
version and to build a new associate name for the case where
the supplied associate name is already used for that purpose.
* resolve.cc (resolve_assoc_var): Call gfc_is_ptr_fcn to allow
associate names with pointer function targets to be used in
variable definition context.
* trans-decl.cc (gfc_get_symbol_decl): Unlimited polymorphic
variables need deferred initialisation of the vptr.
(gfc_trans_deferred_vars): Do the vptr initialisation.
* trans-stmt.cc (trans_associate_var): Ensure that a pointer
associate name points to the target of the selector and not
the selector itself.
gcc/testsuite/
PR fortran/87477
PR fortran/107900
* gfortran.dg/pr107900.f90 : New test
PR fortran/110224
* gfortran.dg/pr110224.f90 : New test
PR fortran/88688
* gfortran.dg/pr88688.f90 : New test
PR fortran/94380
* gfortran.dg/pr94380.f90 : New test
PR fortran/95398
* gfortran.dg/pr95398.f90 : Set -std=f2008, bump the line
numbers in the error tests by two and change the text in two.
next prev parent reply other threads:[~2023-06-21 16:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-87477-4@http.gcc.gnu.org/bugzilla/>
2020-07-05 18:32 ` anlauf at gcc dot gnu.org
2021-09-10 20:08 ` anlauf at gcc dot gnu.org
2023-02-11 18:20 ` anlauf at gcc dot gnu.org
2023-03-29 8:45 ` pault at gcc dot gnu.org
2023-04-08 8:04 ` cvs-commit at gcc dot gnu.org
2023-04-08 9:29 ` pault at gcc dot gnu.org
2023-04-08 9:30 ` pault at gcc dot gnu.org
2023-04-08 9:31 ` pault at gcc dot gnu.org
2023-04-08 9:31 ` pault at gcc dot gnu.org
2023-04-08 9:32 ` pault at gcc dot gnu.org
2023-04-08 9:32 ` pault at gcc dot gnu.org
2023-04-08 9:33 ` pault at gcc dot gnu.org
2023-04-08 9:35 ` pault at gcc dot gnu.org
2023-04-08 13:00 ` pault at gcc dot gnu.org
2023-06-01 13:52 ` pault at gcc dot gnu.org
2023-06-02 7:41 ` cvs-commit at gcc dot gnu.org
2023-06-02 7:52 ` pault at gcc dot gnu.org
2023-06-02 7:59 ` pault at gcc dot gnu.org
2023-06-02 8:02 ` pault at gcc dot gnu.org
2023-06-02 8:16 ` pault at gcc dot gnu.org
2023-06-02 8:24 ` pault at gcc dot gnu.org
2023-06-02 8:28 ` pault at gcc dot gnu.org
2023-06-02 8:40 ` pault at gcc dot gnu.org
2023-06-02 8:41 ` pault at gcc dot gnu.org
2023-06-02 8:42 ` pault at gcc dot gnu.org
2023-06-02 8:44 ` pault at gcc dot gnu.org
2023-06-02 8:52 ` pault at gcc dot gnu.org
2023-06-02 8:55 ` pault at gcc dot gnu.org
2023-06-02 9:16 ` pault at gcc dot gnu.org
2023-06-08 6:11 ` cvs-commit at gcc dot gnu.org
2023-06-08 6:20 ` pault at gcc dot gnu.org
2023-06-08 6:21 ` pault at gcc dot gnu.org
2023-06-21 16:06 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-21 21:05 ` pault at gcc dot gnu.org
2023-06-21 21:05 ` pault at gcc dot gnu.org
2023-06-28 16:39 ` pault at gcc dot gnu.org
2023-08-27 8:51 ` cvs-commit at gcc dot gnu.org
2024-03-06 15:19 ` pault at gcc dot gnu.org
2024-03-15 6:53 ` cvs-commit at gcc dot gnu.org
2024-03-15 7:07 ` pault at gcc dot gnu.org
2024-03-15 7:09 ` pault at gcc dot gnu.org
2024-04-03 18:56 ` anlauf at gcc dot gnu.org
2024-04-04 6:27 ` 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-87477-4-ja2ZsjiBXw@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).