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: Sat, 08 Apr 2023 08:04:30 +0000	[thread overview]
Message-ID: <bug-87477-4-rsJJI0PF1L@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 #2 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:eac493851f07df98213ecf67a5e9ab41a7babcd2

commit r13-7121-geac493851f07df98213ecf67a5e9ab41a7babcd2
Author: Paul Thomas <pault@gcc.gnu.org>
Date:   Sat Apr 8 09:04:13 2023 +0100

    Fortran: Fix some of the bugs in associate [PR87477]

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

    gcc/fortran
            PR fortran/87477
            * iresolve.cc (gfc_resolve_adjustl, gfc_resolve_adjustr): if
            string length is deferred use the string typespec for result.
            * resolve.cc (resolve_assoc_var): Handle parentheses around the
            target expression.
            (resolve_block_construct): Remove unnecessary static decls.
            * trans-array.cc (gfc_conv_expr_descriptor): Guard string len
            expression in condition. Improve handling of string length and
            span, especially for substrings of the descriptor.
            (duplicate_allocatable): Make element type more explicit with
            'eltype'.
            * trans-decl.cc (gfc_get_symbol_decl): Emit a fatal error with
            appropriate message instead of ICE if symbol type is unknown.
            (gfc_generate_function_code): Set current locus to proc_sym
            declared_at.
            * trans-expr.cc (gfc_get_expr_charlen): Retain last charlen in
            'previous' and use if end expression in substring reference is
            null.
            (gfc_conv_string_length): Use gfc_conv_expr_descriptor if
            'expr_flat' is an array. Add post block to catch deallocation
            of temporaries.
            (gfc_conv_procedure_call): Assign the parmse string length to
            the expression string length, if it is deferred.
            (gfc_trans_alloc_subarray_assign): If this is a deferred string
            length component, store the string length in the hidden comp.
            Update the typespec length accordingly. Generate a new type
            spec for the call to gfc_duplicate-allocatable in this case.
            * trans-io.cc (gfc_trans_transfer): Scalarize transfer of
            deferred character array components.

    gcc/testsuite/
            PR fortran/87477
            * gfortran.dg/associate_47.f90 : Enable substring test.
            * gfortran.dg/associate_51.f90 : Update an error message.
            * gfortran.dg/goacc/array-with-dt-2.f90 : Add span to
            uninitialzed dg-warnings.

            PR fortran/85686
            PR fortran/88247
            PR fortran/91941
            PR fortran/92779
            PR fortran/93339
            PR fortran/93813
            PR fortran/100948
            PR fortran/102106
            * gfortran.dg/associate_60.f90 : New test

            PR fortran/98408
            * gfortran.dg/pr98408.f90 : New test

            PR fortran/105205
            * gfortran.dg/pr105205.f90 : New test

            PR fortran/106918
            * gfortran.dg/pr106918.f90 : New test

  parent reply	other threads:[~2023-04-08  8:04 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 [this message]
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
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-rsJJI0PF1L@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).