public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/106050] ICE in reject_statement, at fortran/parse.cc:2879 Date: Tue, 21 Jun 2022 20:47:24 +0000 [thread overview] Message-ID: <bug-106050-4-LanivhnPmw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106050-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106050 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2022-06-21 CC| |kargl at gcc dot gnu.org --- Comment #1 from kargl at gcc dot gnu.org --- With torched input, I might expect the symbol table to get sideways. Before asserting the reference count is zero, check if the count is negative and an error message has already been emitted. diff --git a/gcc/fortran/symbol.cc b/gcc/fortran/symbol.cc index 7a80dfd063b..3aa2b9bd962 100644 --- a/gcc/fortran/symbol.cc +++ b/gcc/fortran/symbol.cc @@ -3106,6 +3106,7 @@ gfc_free_symbol (gfc_symbol *&sym) void gfc_release_symbol (gfc_symbol *&sym) { + if (sym == NULL) return; @@ -3123,6 +3124,14 @@ gfc_release_symbol (gfc_symbol *&sym) if (sym->refs > 0) return; + if (sym->refs < 0) + { + int ecnt; + gfc_get_errors (NULL, &ecnt); + if (ecnt > 0) + return; + } + gcc_assert (sym->refs == 0); gfc_free_symbol (sym); }
next prev parent reply other threads:[~2022-06-21 20:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-21 18:53 [Bug fortran/106050] New: " gscfq@t-online.de 2022-06-21 20:47 ` kargl at gcc dot gnu.org [this message] 2022-06-27 8:48 ` [Bug fortran/106050] ICE in reject_statement, at fortran/parse.cc:2879 since r8-3056-g5bab4c9631c478b7 marxin at gcc dot gnu.org 2023-06-06 19:18 ` kargl at gcc dot gnu.org 2023-07-10 16:20 ` pault at gcc dot gnu.org 2023-07-10 16:29 ` pault at gcc dot gnu.org 2023-07-10 18:15 ` mikael at gcc dot gnu.org 2023-07-11 11:24 ` mikael at gcc dot gnu.org 2023-07-11 11:43 ` pault at gcc dot gnu.org 2023-07-13 19:24 ` cvs-commit at gcc dot gnu.org 2023-09-12 8:36 ` mikael at gcc dot gnu.org 2023-09-15 17:24 ` mikael 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-106050-4-LanivhnPmw@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).