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: *Ping* [PATCH] PR fortran/104210 - [11/12 Regression] ICE in gfc_zero_size_array, at fortran/arith.cc:1685
Date: Mon, 4 Apr 2022 18:18:26 -0700 [thread overview]
Message-ID: <570bc8cc-4c91-5c8f-778f-36d820451d22@gmail.com> (raw)
In-Reply-To: <c047483e-b065-08ed-fea3-ea30d35350ee@gmx.de>
On 4/4/22 12:09 PM, Harald Anlauf via Fortran wrote:
> Am 29.03.22 um 23:41 schrieb Harald Anlauf via Fortran:
>> Dear all,
>>
>> during error recovery on invalid declarations of functions as
>> coarrays we may hit multiple places with NULL pointer dereferences.
>> The attached patch provides a minimal and conservative solution.
>>
>> Regtested on x86_64-pc-linux-gnu. OK for mainline/11-branch?
>>
>> Thanks,
>> Harald
>>
>
Patch looks OK Harald, OK.
Thanks,
Jerry
prev parent reply other threads:[~2022-04-05 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 21:41 Harald Anlauf
2022-04-04 19:09 ` *Ping* " Harald Anlauf
2022-04-04 19:09 ` Harald Anlauf
2022-04-05 1:18 ` 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=570bc8cc-4c91-5c8f-778f-36d820451d22@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).