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/102331] ICE in attr_decl1, at fortran/decl.c:8691 Date: Mon, 27 Mar 2023 02:00:18 +0000 [thread overview] Message-ID: <bug-102331-4-B7g7PupgRK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102331-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102331 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jerry DeLisle <jvdelisle@gcc.gnu.org>: https://gcc.gnu.org/g:82ec75a726b3f8f874dacb0cb342c9bbd1233cc0 commit r12-9320-g82ec75a726b3f8f874dacb0cb342c9bbd1233cc0 Author: Jerry DeLisle <jvdelisle@gcc.gnu.org> Date: Sun Mar 26 18:44:35 2023 -0700 Fortran: Modify checks to avoid referencing NULL pointer. Backport from mainline. gcc/fortran/ChangeLog: PR fortran/102331 * 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: PR fortran/102331 * gfortran.dg/class_result_4.f90: Update error message check. * gfortran.dg/pr85779_3.f90: Update error message check.
next prev parent reply other threads:[~2023-03-27 2:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-14 17:29 [Bug fortran/102331] New: " gscfq@t-online.de 2021-09-14 17:29 ` [Bug fortran/102331] " gscfq@t-online.de 2021-09-15 8:51 ` marxin at gcc dot gnu.org 2021-09-15 17:20 ` kargl at gcc dot gnu.org 2021-09-15 20:57 ` anlauf at gcc dot gnu.org 2021-09-15 21:59 ` sgk at troutmask dot apl.washington.edu 2022-12-26 19:55 ` jvdelisle at gcc dot gnu.org 2022-12-26 20:14 ` jvdelisle at gcc dot gnu.org 2023-01-14 3:29 ` jvdelisle at gcc dot gnu.org 2023-01-18 1:37 ` jvdelisle at gcc dot gnu.org 2023-03-27 2:00 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-29 22:06 ` 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-102331-4-B7g7PupgRK@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: linkBe 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).