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: fix DATA and derived types with pointer components [PR114474]
Date: Wed, 27 Mar 2024 19:51:51 -0700	[thread overview]
Message-ID: <be4897ff-0d3c-4878-97a7-8fcc7eba67d5@gmail.com> (raw)
In-Reply-To: <trinity-4345e5a4-71e7-442a-ba24-0037288a630a-1711572127223@3c-app-gmx-bap43>

On 3/27/24 1:42 PM, Harald Anlauf wrote:
> Dear all,
> 
> the attached patch fixes a 10+ regression for cases where a
> derived type with a pointer component is used in a DATA statement.
> The failure looked obscure, see testcase comments, and pointed
> to a possible issue in the resolution (order).  For the failing
> test, the target variable was seen with ts.type == BT_PROCEDURE
> instead of its actual type.  For this reason, I restricted the
> fixup as much as possible.
> 
> For details, please see the commit message.
> 
> Testcase cross-checked with NAG.
> 
> Regtested on x86_64-pc-linux-gnu.  OK for mainline?
> 
> If this fix survives broader testing, I would like to backport.
> 
> Thanks,
> Harald
> 
> P.S.: while trying to extend coverage of conforming code, I had
> much fun also with other compilers (e.g. NAG panicking...)
> 

OK, for trunk and we will see how it survives for a bit before back port.

Jerry -

      reply	other threads:[~2024-03-28  2:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 20:42 Harald Anlauf
2024-03-28  2:51 ` 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=be4897ff-0d3c-4878-97a7-8fcc7eba67d5@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).