public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry D <jvdelisle2@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: deferred length of character variables shall not get lost [PR113911]
Date: Fri, 16 Feb 2024 16:32:29 -0800	[thread overview]
Message-ID: <eb9479bf-28e1-42a7-abf0-b5185346151e@gmail.com> (raw)
In-Reply-To: <trinity-3bf7068a-de91-443a-87a9-672e84d8a6bd-1708119615252@3c-app-gmx-bs43>

On 2/16/24 1:40 PM, Harald Anlauf wrote:
> Dear all,
> 
> this patch fixes a regression which was a side-effect of r14-8947,
> losing the length of a deferred-length character variable when
> passed as a dummy.
> 
> The new testcase provides a workout for deferred length to improve
> coverage in the testsuite.  Another temporarily disabled test was
> re-enabled.
> 
> Regtested on x86_64-pc-linux-gnu.  OK for mainline?
> 
> Thanks,
> Harald
> 

Yes OK for mainline.

Thanks,

Jerry

      reply	other threads:[~2024-02-17  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 21:40 Harald Anlauf
2024-02-17  0:32 ` Jerry D [this message]

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=eb9479bf-28e1-42a7-abf0-b5185346151e@gmail.com \
    --to=jvdelisle2@gmail.com \
    --cc=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).