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/110882] ICE with -fanalyzer on zero-sized array Date: Wed, 02 Aug 2023 22:23:41 +0000 [thread overview] Message-ID: <bug-110882-4-B0uJaQxm05@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110882-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110882 --- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> --- It's failing this assertion: #1 0x00000000016e2295 in ana::binding_key::make (mgr=0x7fffffff91d8, r=0x3275340) at ../../src/gcc/analyzer/store.cc:132 132 gcc_assert (bit_size > 0); (gdb) list 127 { 128 bit_size_t bit_size; 129 if (r->get_bit_size (&bit_size)) 130 { 131 /* Must be non-empty. */ 132 gcc_assert (bit_size > 0); 133 return mgr->get_concrete_binding (offset.get_bit_offset (), 134 bit_size); 135 } 136 else
next prev parent reply other threads:[~2023-08-02 22:23 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-02 22:23 [Bug analyzer/110882] New: " dmalcolm at gcc dot gnu.org 2023-08-02 22:23 ` dmalcolm at gcc dot gnu.org [this message] 2023-08-02 22:24 ` [Bug analyzer/110882] " dmalcolm at gcc dot gnu.org 2023-08-03 13:48 ` [Bug analyzer/110882] [13/14 Regression] " cvs-commit at gcc dot gnu.org 2023-08-03 13:54 ` [Bug analyzer/110882] [13 " dmalcolm at gcc dot gnu.org 2023-08-03 14:47 ` cvs-commit at gcc dot gnu.org 2023-08-03 14:53 ` dmalcolm at gcc dot gnu.org 2023-10-17 10:28 ` rguenth at gcc dot gnu.org 2024-05-09 17:11 ` cvs-commit at gcc dot gnu.org 2024-05-09 17:11 ` cvs-commit at gcc dot gnu.org 2024-05-09 17:52 ` [Bug analyzer/110882] " 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-110882-4-B0uJaQxm05@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).