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 analyzer/107158] internal compiler error: in get_or_create_cluster, at analyzer/store.cc:2832 Date: Wed, 05 Oct 2022 18:08:08 +0000 [thread overview] Message-ID: <bug-107158-4-CbEjMEGFFO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107158-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107158 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>: https://gcc.gnu.org/g:ef878564140cbcf23f479da88e07e5a996cec6bb commit r13-3096-gef878564140cbcf23f479da88e07e5a996cec6bb Author: David Malcolm <dmalcolm@redhat.com> Date: Wed Oct 5 14:07:47 2022 -0400 analyzer: add regression test for PR 107158 PR analyzer/107158 reports an ICE when using -fanalyzer -fanalyzer-call-summaries on a particular source file. It turns out I just fixed this ICE in r13-3094-g6832c95c0e1a58. This followup patch adds a somewhat reduced reproducer as a regression test. Unfortunately, although the ICE is fixed, there are two false positives from -Wanalyzer-malloc-leak on the test case, so I'm going to use PR analyzer/107158 for tracking those false positives. gcc/testsuite/ChangeLog: PR analyzer/107158 * gcc.dg/analyzer/call-summaries-pr107158.c: New test. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-10-05 18:08 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-05 16:00 [Bug analyzer/107158] New: " urs at akk dot org 2022-10-05 16:01 ` [Bug analyzer/107158] " urs at akk dot org 2022-10-05 17:28 ` dmalcolm at gcc dot gnu.org 2022-10-05 18:08 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-05 18:15 ` [Bug analyzer/107158] False postives from -Wanalyzer-malloc-leak on tin-2.6.2 dmalcolm at gcc dot gnu.org 2022-10-05 20:22 ` urs at akk dot org 2022-10-06 14:00 ` dmalcolm at gcc dot gnu.org 2022-10-06 19:48 ` cvs-commit at gcc dot gnu.org 2022-10-06 19:54 ` dmalcolm at gcc dot gnu.org 2022-11-24 21:11 ` urs at akk dot 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-107158-4-CbEjMEGFFO@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).