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/107788] [13 Regression] ICE in wide_int_to_tree_1, at tree.cc:1757 since r13-4074-g86a90006864840c2
Date: Tue, 22 Nov 2022 00:10:20 +0000 [thread overview]
Message-ID: <bug-107788-4-ZgJWwejmZ0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107788-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107788
--- 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:4e4e45a4fd341174d8231ee6a99e6fe308904f8f
commit r13-4221-g4e4e45a4fd341174d8231ee6a99e6fe308904f8f
Author: David Malcolm <dmalcolm@redhat.com>
Date: Mon Nov 21 19:08:18 2022 -0500
analyzer: fix ICE on 'bind' that returns a struct [PR107788]
gcc/analyzer/ChangeLog:
PR analyzer/107788
* region-model.cc (region_model::update_for_int_cst_return):
Require that the return type be an integer type.
(region_model::update_for_nonzero_return): Likewise.
gcc/testsuite/ChangeLog:
PR analyzer/107788
* g++.dg/analyzer/fd-bind-pr107783.C: New test.
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-11-22 0:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 10:51 [Bug analyzer/107788] New: [13 Regression] ICE in wide_int_to_tree_1, at tree.cc:1757 asolokha at gmx dot com
2022-11-21 12:07 ` [Bug analyzer/107788] " marxin at gcc dot gnu.org
2022-11-21 12:07 ` [Bug analyzer/107788] [13 Regression] ICE in wide_int_to_tree_1, at tree.cc:1757 since r13-4074-g86a90006864840c2 marxin at gcc dot gnu.org
2022-11-21 15:54 ` pinskia at gcc dot gnu.org
2022-11-22 0:10 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-22 0:25 ` dmalcolm at gcc dot gnu.org
2022-11-22 22:32 ` cvs-commit at gcc dot gnu.org
2022-11-22 22:45 ` 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-107788-4-ZgJWwejmZ0@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: link
Be 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).