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/104573] ICE in resolve_structure_cons, at fortran/resolve.cc:1299 Date: Wed, 02 Mar 2022 18:23:46 +0000 [thread overview] Message-ID: <bug-104573-4-lWThZskwrj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104573-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104573 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:12463f1ecbcb30b39b8212454a6e598645123305 commit r12-7456-g12463f1ecbcb30b39b8212454a6e598645123305 Author: Harald Anlauf <anlauf@gmx.de> Date: Tue Mar 1 23:13:17 2022 +0100 Fortran: error recovery after invalid assumed type declaration gcc/fortran/ChangeLog: PR fortran/104573 * resolve.cc (resolve_structure_cons): Avoid NULL pointer dereference when there is no valid component. gcc/testsuite/ChangeLog: PR fortran/104573 * gfortran.dg/assumed_type_14.f90: New test.
next prev parent reply other threads:[~2022-03-02 18:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-16 17:35 [Bug fortran/104573] New: " gscfq@t-online.de 2022-02-16 20:00 ` [Bug fortran/104573] " kargl at gcc dot gnu.org 2022-02-16 20:10 ` anlauf at gcc dot gnu.org 2022-02-16 20:25 ` sgk at troutmask dot apl.washington.edu 2022-02-16 20:32 ` anlauf at gcc dot gnu.org 2022-02-16 20:39 ` sgk at troutmask dot apl.washington.edu 2022-02-16 20:59 ` anlauf at gcc dot gnu.org 2022-02-16 21:20 ` anlauf at gcc dot gnu.org 2022-03-02 18:23 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-02 18:25 ` 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-104573-4-lWThZskwrj@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).