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: Thu, 08 Jun 2023 06:11:42 +0000	[thread overview]
Message-ID: <bug-87477-4-e5bohwrumV@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 #4 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:d08f2e4f74583e27002368989bba197f8eb7f6d2

commit r14-1629-gd08f2e4f74583e27002368989bba197f8eb7f6d2
Author: Paul Thomas <pault@gcc.gnu.org>
Date:   Thu Jun 8 07:11:32 2023 +0100

    Fortran: Fix some more blockers in associate meta-bug [PR87477]

    2023-06-08  Paul Thomas  <pault@gcc.gnu.org>

    gcc/fortran
            PR fortran/87477
            PR fortran/99350
            PR fortran/107821
            PR fortran/109451
            * decl.cc (char_len_param_value): Simplify a copy of the expr
            and replace the original if there is no error.
            * gfortran.h : Remove the redundant field 'rankguessed' from
            'gfc_association_list'.
            * resolve.cc (resolve_assoc_var): Remove refs to 'rankguessed'.
            (resolve_variable): Associate names with constant or structure
            constructor targets cannot have array refs.
            * trans-array.cc (gfc_conv_expr_descriptor): Guard expression
            character length backend decl before using it. Suppress the
            assignment if lhs equals rhs.
            * trans-io.cc (gfc_trans_transfer): Scalarize transfer of
            associate variables pointing to a variable. Add comment.
            * trans-stmt.cc (trans_associate_var): Remove requirement that
            the character length be deferred before assigning the value
            returned by gfc_conv_expr_descriptor. Also, guard the backend
            decl before testing with VAR_P.

    gcc/testsuite/
            PR fortran/99350
            * gfortran.dg/pr99350.f90 : New test.

            PR fortran/107821
            * gfortran.dg/associate_5.f03 : Changed error message.
            * gfortran.dg/pr107821.f90 : New test.

            PR fortran/109451
            * gfortran.dg/associate_61.f90 : New test

  parent reply	other threads:[~2023-06-08  6:11 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 [this message]
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
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-e5bohwrumV@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).