public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arsen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/108171] [13/14 Regression] ICE in binding_key::make, at analyzer/store.cc:132 since r13-4529-gdfe2ef7f2b6cac70 Date: Sun, 30 Apr 2023 20:41:33 +0000 [thread overview] Message-ID: <bug-108171-4-GYSuRQtiN0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108171-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108171 Arsen Arsenović <arsen at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arsen at gcc dot gnu.org --- Comment #3 from Arsen Arsenović <arsen at gcc dot gnu.org> --- I believe the following test case is of the same issue: struct nl_context { void *cmd_private }; struct sfeatures_context { int a; int req_mask[0] }; set_sf_req_mask_idx; fill_sfeatures_bitmap(struct nl_context *nlctx) { while (nlctx) { fill_legacy_flag(); struct nl_context __trans_tmp_1 = *nlctx; struct sfeatures_context *sfctx = __trans_tmp_1.cmd_private; sfctx->req_mask[set_sf_req_mask_idx] |= 1; } } nl_sfeatures() { struct nl_context nlctx; struct sfeatures_context *sfctx; nlctx.cmd_private = &sfctx; sfctx = 0; fill_sfeatures_bitmap(&nlctx); } note that making req_mask a C99 FAM by dropping the zero makes the ICE go away
next prev parent reply other threads:[~2023-04-30 20:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-19 6:30 [Bug analyzer/108171] New: [13 Regression] ICE in binding_key::make, at analyzer/store.cc:132 asolokha at gmx dot com 2022-12-19 8:30 ` [Bug analyzer/108171] " rguenth at gcc dot gnu.org 2022-12-19 14:25 ` [Bug analyzer/108171] [13 Regression] ICE in binding_key::make, at analyzer/store.cc:132 since r13-4529-gdfe2ef7f2b6cac70 marxin at gcc dot gnu.org 2023-04-26 6:57 ` [Bug analyzer/108171] [13/14 " rguenth at gcc dot gnu.org 2023-04-30 20:41 ` arsen at gcc dot gnu.org [this message] 2023-07-27 9:24 ` rguenth at gcc dot gnu.org 2023-08-03 14:26 ` 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 2024-05-09 17:11 ` cvs-commit 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-108171-4-GYSuRQtiN0@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).