public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/98969] [11 Regression] ICE: Segmentation fault (in print_mem_ref) Date: Fri, 05 Feb 2021 14:18:48 +0000 [thread overview] Message-ID: <bug-98969-4-AxP9oIV62M@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98969-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98969 David Malcolm <dmalcolm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|msebor at gcc dot gnu.org |dmalcolm at gcc dot gnu.org --- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Mine; the analyzer shouldn't ICE by constructing malformed trees. Also, the leak diagnostic is arguably a false positive in that (struct TYPE_14__ *) _round_2_cb_n_0 is still effectively reachable by the caller after the function returns.
next prev parent reply other threads:[~2021-02-05 14:18 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-04 17:06 [Bug c/98969] New: " asolokha at gmx dot com 2021-02-04 20:34 ` [Bug c/98969] " msebor at gcc dot gnu.org 2021-02-04 20:50 ` msebor at gcc dot gnu.org 2021-02-04 20:52 ` jakub at gcc dot gnu.org 2021-02-05 8:15 ` [Bug analyzer/98969] " rguenth at gcc dot gnu.org 2021-02-05 14:08 ` jakub at gcc dot gnu.org 2021-02-05 14:18 ` dmalcolm at gcc dot gnu.org [this message] 2021-02-06 16:16 ` msebor at gcc dot gnu.org 2021-02-06 17:10 ` msebor at gcc dot gnu.org 2021-02-11 1:59 ` dmalcolm at gcc dot gnu.org 2021-02-12 1:32 ` cvs-commit at gcc dot gnu.org 2021-02-12 1:36 ` dmalcolm at gcc dot gnu.org 2021-02-17 15:38 ` cvs-commit at gcc dot gnu.org 2021-02-17 15:40 ` dmalcolm 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-98969-4-AxP9oIV62M@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).