From: Harald Anlauf <anlauf@gmx.de>
To: Jerry DeLisle <jvdelisle@protonmail.com>, gfortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] ICE in attr_decl1, at fortran/decl.c:8691
Date: Tue, 27 Dec 2022 12:04:06 +0100 [thread overview]
Message-ID: <ac3ad4fd-6829-0d69-9af7-bd2d7cd7e998@gmx.de> (raw)
In-Reply-To: <7802b3ba-cf1d-84eb-6e64-e470ef8e911a@protonmail.com>
Hi Jerry,
Am 26.12.22 um 23:26 schrieb Jerry DeLisle via Gcc-patches:
> The attached patch was provided by Steve Kargl. After exploring for
> possible other checks I settled on leaving the patch intact.
>
> Two existing test cases updated as different but sensible error messages
> resulted.
I think this is fine. The error message for CLASS is
now arguably more consistent with TYPE.
> Regression tested on main line.
>
> OK to commit?
Regarding the format of the commit message: if you want
bugzilla to get updated properly, please consider adding
PR/fortran ###### to the respective parts below.
It is also custom to have a one-line summary including
e.g. [PR######] to make it easier for others to relate
a commit to bugzilla.
OK with these things fixed.
Thanks for taking this!
Harald
> Regards,
>
> Jerry
>
> Author: Steve Kargl <kargl@gcc.gnu.org>
> Date: Mon Dec 26 14:07:04 2022 -0800
>
> Modify checks to avoid referencing NULL pointer.
> Update test cases with error messages that changed as a result.
>
> gcc/fortran/ChangeLog:
>
> * decl.cc (attr_decl1): Guard against NULL pointer.
> * parse.cc (match_deferred_characteristics): Include
> BT_CLASS in check for
> derived being undefined.
>
> gcc/testsuite/ChangeLog:
>
> * gfortran.dg/class_result_4.f90: Update error message check.
> * gfortran.dg/pr85779_3.f90: Update error message check.
prev parent reply other threads:[~2022-12-27 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 22:26 Jerry DeLisle
2022-12-27 11:04 ` Harald Anlauf [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=ac3ad4fd-6829-0d69-9af7-bd2d7cd7e998@gmx.de \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@protonmail.com \
/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).