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/113222] ICE with -fanalyzer seen on Linux kernel kernel/sched/core.c Date: Thu, 04 Jan 2024 14:13:51 +0000 [thread overview] Message-ID: <bug-113222-4-itWMY8SdMU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113222-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113222 --- Comment #2 from GCC 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:db5b01d282a0e3ddcac737e55f9758c8b081cf4b commit r14-6917-gdb5b01d282a0e3ddcac737e55f9758c8b081cf4b Author: David Malcolm <dmalcolm@redhat.com> Date: Thu Jan 4 09:12:40 2024 -0500 analyzer: handle arrays of unknown size in access diagrams [PR113222] gcc/analyzer/ChangeLog: PR analyzer/113222 * access-diagram.cc (valid_region_spatial_item::add_boundaries): Handle TYPE_DOMAIN being null. (valid_region_spatial_item::add_array_elements_to_table): Likewise. gcc/testsuite/ChangeLog: PR analyzer/113222 * gcc.dg/analyzer/out-of-bounds-diagram-pr113222.c: New test. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2024-01-04 14:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-03 18:28 [Bug analyzer/113222] New: " dmalcolm at gcc dot gnu.org 2024-01-03 20:06 ` [Bug analyzer/113222] " dmalcolm at gcc dot gnu.org 2024-01-04 14:13 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-04 14:59 ` 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-113222-4-itWMY8SdMU@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).