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/113911] [14 Regression] Length is lost passing deferred-length character to subroutine
Date: Sat, 17 Feb 2024 14:07:30 +0000	[thread overview]
Message-ID: <bug-113911-4-l3WRFNlKZI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113911-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:76aac40f5ecbc9cfb3b8734d181599e1b5a24bdf

commit r14-9045-g76aac40f5ecbc9cfb3b8734d181599e1b5a24bdf
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Fri Feb 16 22:33:16 2024 +0100

    Fortran: deferred length of character variables shall not get lost
[PR113911]

            PR fortran/113911

    gcc/fortran/ChangeLog:

            * trans-array.cc (gfc_trans_deferred_array): Do not clobber
            deferred length for a character variable passed as dummy argument.

    gcc/testsuite/ChangeLog:

            * gfortran.dg/allocatable_length_2.f90: New test.
            * gfortran.dg/bind_c_optional-2.f90: Enable deferred-length test.

  parent reply	other threads:[~2024-02-17 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 18:28 [Bug fortran/113911] New: " anlauf at gcc dot gnu.org
2024-02-13 18:29 ` [Bug fortran/113911] " anlauf at gcc dot gnu.org
2024-02-13 19:23 ` anlauf at gcc dot gnu.org
2024-02-13 19:51 ` anlauf at gcc dot gnu.org
2024-02-13 20:02 ` anlauf at gcc dot gnu.org
2024-02-13 20:33 ` anlauf at gcc dot gnu.org
2024-02-13 20:43 ` anlauf at gcc dot gnu.org
2024-02-16 21:44 ` anlauf at gcc dot gnu.org
2024-02-17 14:07 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-17 20:19 ` 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-113911-4-l3WRFNlKZI@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).