public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99711] Crash when reading an allocated character array in namelist
Date: Thu, 31 Aug 2023 17:20:09 +0000	[thread overview]
Message-ID: <bug-99711-4-iY5ZYp2M21@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99711-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #19 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Aug 31, 2023 at 12:58:15PM +0000, philippe.wautelet at aero dot
obs-mip.fr wrote:
> 
> What is the status of this bug?
> 
> It seems that it is not present any more in the 12.x and 13.x GCC versions.
> 

Looks like it is fixed by the patch for some other bug report.
A scan of gcc/fortran/ChangeLog shows a number patches that
tinker with the character length for deferred length strings.
I don't which one is the responsiblei, and since I don't use 
git (other than for trivial 'git diff' and 'git pull') doing a
bisection is beyond my skillset.

Someone should likely convert your testcase into something
that the testsuite can digest, and commit it.

  parent reply	other threads:[~2023-08-31 17:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 14:02 [Bug fortran/99711] New: " phil1691 at gmail dot com
2021-03-23  1:11 ` [Bug fortran/99711] " jvdelisle at gcc dot gnu.org
2021-03-23  2:11 ` kargl at gcc dot gnu.org
2021-03-23  2:29 ` jvdelisle at gcc dot gnu.org
2021-03-23  2:41 ` jvdelisle at gcc dot gnu.org
2021-03-23  6:16 ` sgk at troutmask dot apl.washington.edu
2021-03-23  7:37 ` philippe.wautelet at aero dot obs-mip.fr
2021-03-24  2:41 ` jvdelisle at gcc dot gnu.org
2021-03-24  3:15 ` jvdelisle at gcc dot gnu.org
2021-03-24  5:35 ` sgk at troutmask dot apl.washington.edu
2021-03-24  5:45 ` sgk at troutmask dot apl.washington.edu
2021-03-25  3:32 ` jvdelisle at gcc dot gnu.org
2021-03-26  1:47 ` jvdelisle at gcc dot gnu.org
2021-03-26  2:25 ` jvdelisle at gcc dot gnu.org
2021-03-26  2:38 ` jvdelisle at gcc dot gnu.org
2021-03-26  6:04 ` sgk at troutmask dot apl.washington.edu
2021-03-26 23:38 ` jvdelisle at gcc dot gnu.org
2021-03-27  3:14 ` jvdelisle at gcc dot gnu.org
2023-08-31 12:58 ` philippe.wautelet at aero dot obs-mip.fr
2023-08-31 17:20 ` sgk at troutmask dot apl.washington.edu [this message]
2023-08-31 17:22 ` kargl 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-99711-4-iY5ZYp2M21@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).