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/102003] [PDT] Length of character component not simplified
Date: Fri, 26 Apr 2024 07:07:56 +0000	[thread overview]
Message-ID: <bug-102003-4-Ym0VdKjq6n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102003-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102003

--- Comment #6 from GCC 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:e207b67fcde224f2be0c79bf2a24f7fc75b6f481

commit r13-8651-ge207b67fcde224f2be0c79bf2a24f7fc75b6f481
Author: Andre Vehreschild <vehre@gcc.gnu.org>
Date:   Wed Jul 12 12:51:30 2023 +0200

    gfortran: Allow ref'ing PDT's len() in parameter-initializer.

    Fix declaring a parameter initialized using a pdt_len reference
    not simplifying the reference to a constant.

    2023-07-12  Andre Vehreschild  <vehre@gcc.gnu.org>

    gcc/fortran/ChangeLog:

            PR fortran/102003
            * expr.cc (find_inquiry_ref): Replace len of pdt_string by
            constant.
            (simplify_ref_chain): Ensure input to find_inquiry_ref is
            NULL.
            (gfc_match_init_expr): Prevent PDT analysis for function calls.
            (gfc_pdt_find_component_copy_initializer): Get the initializer
            value for given component.
            * gfortran.h (gfc_pdt_find_component_copy_initializer): New
            function.
            * simplify.cc (gfc_simplify_len): Replace len() of PDT with pdt
            component ref or constant.

    gcc/testsuite/ChangeLog:

            * gfortran.dg/pdt_33.f03: New test.

    (cherry picked from commit f9182da3213aa57c16dd0b52862126de4a259f6a)

  parent reply	other threads:[~2024-04-26  7:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 19:11 [Bug fortran/102003] New: " anlauf at gcc dot gnu.org
2022-06-13 13:11 ` [Bug fortran/102003] " wileamyp at outlook dot com
2023-06-30  8:22 ` pault at gcc dot gnu.org
2023-07-10 15:53 ` vehre at gcc dot gnu.org
2023-07-12 11:35 ` cvs-commit at gcc dot gnu.org
2023-07-20 11:56 ` vehre at gcc dot gnu.org
2024-04-26  7:07 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-26 16:51 ` cvs-commit 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-102003-4-Ym0VdKjq6n@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).