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/114874] [14/15 Regression] ICE with select type, type is (character(*)), and substring
Date: Fri, 17 May 2024 14:23:33 +0000	[thread overview]
Message-ID: <bug-114874-4-pIsbmvUzb8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114874-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-14 branch has been updated by Paul Thomas <pault@gcc.gnu.org>:

https://gcc.gnu.org/g:c887341432bb71cf5540d54955ad7265b0aaca77

commit r14-10216-gc887341432bb71cf5540d54955ad7265b0aaca77
Author: Paul Thomas <pault@gcc.gnu.org>
Date:   Fri May 17 15:19:26 2024 +0100

    Fortran: Fix select type regression due to r14-9489 [PR114874]

    2024-05-17  Paul Thomas  <pault@gcc.gnu.org>

    gcc/fortran
            PR fortran/114874
            * gfortran.h: Add 'assoc_name_inferred' to gfc_namespace.
            * match.cc (gfc_match_select_type): Set 'assoc_name_inferred'
            in select type namespace if the selector has inferred type.
            * primary.cc (gfc_match_varspec): If a select type temporary
            is apparently scalar and a left parenthesis has been detected,
            check the current namespace has 'assoc_name_inferred' set. If
            so, set inferred_type.
            * resolve.cc (resolve_variable): If the namespace of a select
            type temporary is marked with 'assoc_name_inferred' call
            gfc_fixup_inferred_type_refs to ensure references are OK.
            (gfc_fixup_inferred_type_refs): Catch invalid array refs..

    gcc/testsuite/
            PR fortran/114874
            * gfortran.dg/pr114874_1.f90: New test for valid code.
            * gfortran.dg/pr114874_2.f90: New test for invalid code.

    (cherry picked from commit 5f5074fe7aaf9524defb265299a985eecba7f914)

  parent reply	other threads:[~2024-05-17 14:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27 20:53 [Bug fortran/114874] New: " anlauf at gcc dot gnu.org
2024-04-27 20:55 ` [Bug fortran/114874] " anlauf at gcc dot gnu.org
2024-04-27 21:05 ` anlauf at gcc dot gnu.org
2024-04-29 20:19 ` anlauf at gcc dot gnu.org
2024-04-29 20:22 ` anlauf at gcc dot gnu.org
2024-04-29 21:39 ` pault at gcc dot gnu.org
2024-04-30  6:43 ` pault at gcc dot gnu.org
2024-04-30  9:32 ` rguenth at gcc dot gnu.org
2024-04-30 17:19 ` pault at gcc dot gnu.org
2024-05-04 21:12 ` pault at gcc dot gnu.org
2024-05-07  7:45 ` rguenth at gcc dot gnu.org
2024-05-17 14:19 ` cvs-commit at gcc dot gnu.org
2024-05-17 14:23 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-17 14:25 ` pault at gcc dot gnu.org
2024-05-22 17:55 ` anlauf 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-114874-4-pIsbmvUzb8@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).