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/96777] [11 Regression] ICE in bind_compound_sval with initializer for incomplete array type Date: Wed, 26 Aug 2020 01:39:55 +0000 [thread overview] Message-ID: <bug-96777-4-0qvauK6I3C@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96777-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96777 --- 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:d88c8df70342fcd6817e23f243ff38d0fe42fc6b commit r11-2854-gd88c8df70342fcd6817e23f243ff38d0fe42fc6b Author: David Malcolm <dmalcolm@redhat.com> Date: Tue Aug 25 09:26:05 2020 -0400 analyzer: fix ICE on initializers for unsized array fields [PR96777] gcc/analyzer/ChangeLog: PR analyzer/96777 * region-model.h (class compound_svalue): Document that all keys must be concrete. (compound_svalue::compound_svalue): Move definition to svalue.cc. * store.cc (binding_map::apply_ctor_to_region): Handle initializers for trailing arrays with incomplete size. * svalue.cc (compound_svalue::compound_svalue): Move definition here from region-model.h. Add assertion that all keys are concrete. gcc/testsuite/ChangeLog: PR analyzer/96777 * gcc.dg/analyzer/pr96777.c: New test.
next prev parent reply other threads:[~2020-08-26 1:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-25 1:50 [Bug analyzer/96777] New: [11 Regression] ICE in bind_compound_sval, at analyzer/store.cc:618 asolokha at gmx dot com 2020-08-25 11:50 ` [Bug analyzer/96777] " rguenth at gcc dot gnu.org 2020-08-25 12:02 ` dmalcolm at gcc dot gnu.org 2020-08-25 13:52 ` [Bug analyzer/96777] [11 Regression] ICE in bind_compound_sval with initializer for incomplete array type dmalcolm at gcc dot gnu.org 2020-08-26 1:39 ` cvs-commit at gcc dot gnu.org [this message] 2020-08-26 1:47 ` 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-96777-4-0qvauK6I3C@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).