public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/78746] charlen_03, charlen_10 ICE
Date: Thu, 07 Jan 2021 19:30:25 +0000 [thread overview]
Message-ID: <bug-78746-4-m0jrPBVmqo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-78746-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78746
--- Comment #24 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:19eb1973321375190485bc49e68992863b1972bf
commit r10-9234-g19eb1973321375190485bc49e68992863b1972bf
Author: Harald Anlauf <anlauf@gmx.de>
Date: Wed Jan 6 19:37:11 2021 +0100
PR fortran/78746 - invalid access after error recovery
The error recovery after an invalid reference to an undefined CLASS
during a TYPE declaration lead to an invalid access. Add a check.
gcc/fortran/ChangeLog:
* resolve.c (resolve_component): Add check for valid CLASS
reference before trying to access CLASS data.
(cherry picked from commit 8b6f1e8f97fe0d435d334075821149dbd85c8266)
next prev parent reply other threads:[~2021-01-07 19:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-78746-4@http.gcc.gnu.org/bugzilla/>
2020-03-21 14:01 ` dcb314 at hotmail dot com
2021-01-04 22:46 ` anlauf at gcc dot gnu.org
2021-01-05 20:42 ` anlauf at gcc dot gnu.org
2021-01-06 18:37 ` cvs-commit at gcc dot gnu.org
2021-01-07 19:30 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-07 19:33 ` cvs-commit at gcc dot gnu.org
2021-01-07 19:41 ` anlauf at gcc dot gnu.org
2021-01-13 11:35 ` dominiq at lps dot ens.fr
2021-01-13 15:42 ` anlauf at gcc dot gnu.org
2021-01-13 16:12 ` dominiq at lps dot ens.fr
2021-01-13 16:34 ` anlauf at gcc dot gnu.org
2021-01-13 20:06 ` anlauf 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-78746-4-m0jrPBVmqo@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).