From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Harald Anlauf via Fortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: fix NULL pointer dereference in gfc_check_dependency [PR108502]
Date: Mon, 23 Jan 2023 13:47:36 -0800 [thread overview]
Message-ID: <Y88AeNvIvHifuLy1@troutmask.apl.washington.edu> (raw)
In-Reply-To: <trinity-a7fd4365-096c-4df3-b654-6912a5dca41d-1674509034609@3c-app-gmx-bap50>
On Mon, Jan 23, 2023 at 10:23:54PM +0100, Harald Anlauf via Fortran wrote:
>
> the code in the PR demonstrates that dependency checking in the
> frontend optimization was not recovering well from invalid code,
> leading to a NULL pointer dereference. An easy and really obvious
> fix.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
Yes. I agree patch looks obvious once the issue is found.
Thanks for the patch.
--
Steve
prev parent reply other threads:[~2023-01-23 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 21:23 Harald Anlauf
2023-01-23 21:45 ` Thomas Koenig
2023-01-23 21:47 ` Steve Kargl [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=Y88AeNvIvHifuLy1@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--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).