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/107486] [13 Regression] ICE when pipe's argument is not a pointer type Date: Thu, 03 Nov 2022 14:22:08 +0000 [thread overview] Message-ID: <bug-107486-4-aMJI7R3qtK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107486-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107486 --- Comment #2 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:5acc10a9ea66411e1712fabc94f9f29892b0d607 commit r13-3626-g5acc10a9ea66411e1712fabc94f9f29892b0d607 Author: David Malcolm <dmalcolm@redhat.com> Date: Thu Nov 3 10:21:00 2022 -0400 analyzer: fix ICE when pipe's arg isn't a pointer [PR107486] gcc/analyzer/ChangeLog: PR analyzer/107486 * analyzer.cc (is_pipe_call_p): New. * analyzer.h (is_pipe_call_p): New decl. * region-model.cc (region_model::on_call_pre): Use it. (region_model::on_call_post): Likewise. gcc/testsuite/ChangeLog: PR analyzer/107486 * gcc.dg/analyzer/pipe-pr107486.c: New test. * gcc.dg/analyzer/pipe-void-return.c: New test. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-11-03 14:22 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-01 5:28 [Bug analyzer/107486] New: [13 Regression] ICE in deref_rvalue, at analyzer/region-model.cc:3317 asolokha at gmx dot com 2022-11-02 15:20 ` [Bug analyzer/107486] [13 Regression] ICE when pipe's argument is not a pointer type dmalcolm at gcc dot gnu.org 2022-11-03 14:22 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-03 14:58 ` dmalcolm at gcc dot gnu.org 2022-11-28 22:08 ` pinskia 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-107486-4-aMJI7R3qtK@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).