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: Fri, 15 Mar 2024 06:53:17 +0000	[thread overview]
Message-ID: <bug-87477-4-l4bbbtQDjE@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 #7 from GCC 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:3fd46d859cda1074125449a4cc680ce59fcebc38

commit r14-9489-g3fd46d859cda1074125449a4cc680ce59fcebc38
Author: Paul Thomas <pault@gcc.gnu.org>
Date:   Fri Mar 15 06:52:59 2024 +0000

    Fortran: Fix class/derived/complex function associate selectors [PR87477]

    2024-03-15  Paul Thomas  <pault@gcc.gnu.org>

    gcc/fortran
            PR fortran/87477
            PR fortran/89645
            PR fortran/99065
            PR fortran/114141
            PR fortran/114280
            * class.cc (gfc_change_class): New function needed for
            associate names, when rank changes or a derived type is
            produced by resolution
            * dump-parse-tree.cc (show_code_node): Make output for SELECT
            TYPE more comprehensible.
            * expr.cc (find_inquiry_ref): Do not simplify expressions of
            an inferred type.
            * gfortran.h : Add 'gfc_association_list' to structure
            'gfc_association_list'. Add prototypes for
            'gfc_find_derived_types', 'gfc_fixup_inferred_type_refs' and
            'gfc_change_class'. Add macro IS_INFERRED_TYPE.
            * match.cc (copy_ts_from_selector_to_associate): Add bolean arg
            'select_type' with default false. If this is a select type name
            and the selector is a inferred type, build the class type and
            apply it to the associate name.
            (build_associate_name): Pass true to 'select_type' in call to
            previous.
            * parse.cc (parse_associate): If the selector is inferred type
            the associate name is too. Make sure that function selector
            class and rank, if known, are passed to the associate name. If
            a function result exists, pass its typespec to the associate
            name.
            * primary.cc (resolvable_fcns): New function to check that all
            the function references are resolvable.
            (gfc_match_varspec): If a scalar derived type select type
            temporary has an array reference, match the array reference,
            treating this in the same way as an equivalence member. Do not
            set 'inquiry' if applied to an unknown type the inquiry name
            is ambiguous with the component of an accessible derived type.
            Check that resolution of the target expression is OK by testing
            if the symbol is declared or is an operator expression, then
            using 'resolvable_fcns' recursively. If all is well, resolve
            the expression. If this is an inferred type with a component
            reference, call 'gfc_find_derived_types' to find a suitable
            derived type. If there is an inquiry ref and the symbol either
            is of unknown type or is inferred to be a derived type, set the
            primary and symbol TKR appropriately.
            * resolve.cc (resolve_variable): Call new function below.
            (gfc_fixup_inferred_type_refs): New function to ensure that the
            expression references for a inferred type are consistent with
            the now fixed up selector.
            (resolve_assoc_var): Ensure that derived type or class function
            selectors transmit the correct arrayspec to the associate name.
            (resolve_select_type): If the selector is an associate name of
            inferred type and has no component references, the associate
            name should have its typespec. Simplify the conversion of a
            class array to class scalar by calling 'gfc_change_class'.
            Make sure that a class, inferred type selector with an array
            ref transfers the typespec from the symbol to the expression.
            * symbol.cc (gfc_set_default_type): If an associate name with
            unknown type has a selector expression, try resolving the expr.
            (find_derived_types, gfc_find_derived_types): New functions
            that search for a derived type with a given name.
            * trans-expr.cc (gfc_conv_variable): Some inferred type exprs
            escape resolution so call 'gfc_fixup_inferred_type_refs'.
            * trans-stmt.cc (trans_associate_var): Tidy up expression for
            'class_target'. Finalize and free class function results.
            Correctly handle selectors that are class functions and class
            array references, passed as derived types.

    gcc/testsuite/
            PR fortran/87477
            PR fortran/89645
            PR fortran/99065
            * gfortran.dg/associate_64.f90 : New test
            * gfortran.dg/associate_66.f90 : New test
            * gfortran.dg/associate_67.f90 : New test

            PR fortran/114141
            * gfortran.dg/associate_65.f90 : New test

            PR fortran/114280
            * gfortran.dg/associate_68.f90 : New test

  parent reply	other threads:[~2024-03-15  6:53 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
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 [this message]
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-l4bbbtQDjE@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).