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/106551] [13 Regression] dup2 causes -fanalyzer ICE in valid_to_unchecked_state, at analyzer/sm-fd.cc:751 Date: Mon, 15 Aug 2022 16:52:49 +0000 [thread overview] Message-ID: <bug-106551-4-EZZZC20b53@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106551-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106551 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Immad Mir <mir@gcc.gnu.org>: https://gcc.gnu.org/g:ed7e7620188dc0e653815bdd40d8802bd5446638 commit r13-2051-ged7e7620188dc0e653815bdd40d8802bd5446638 Author: Immad Mir <mirimmad@outlook.com> Date: Mon Aug 15 22:21:27 2022 +0530 analyzer: fix for ICE in sm-fd.cc [PR106551] This patch fixes the ICE caused by valid_to_unchecked_state in sm-fd.cc by exiting early if first argument of any "dup" functions is invalid. gcc/analyzer/ChangeLog: PR analyzer/106551 * sm-fd.cc (check_for_dup): exit early if first argument is invalid for all dup functions. gcc/testsuite/ChangeLog: PR analyzer/106551 * gcc.dg/analyzer/fd-dup-1.c: New testcase. Signed-off-by: Immad Mir <mirimmad@outlook.com>
next prev parent reply other threads:[~2022-08-15 16:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-08 6:39 [Bug analyzer/106551] New: [13 Regression] dup2 causes -fanalyser " slyfox at gcc dot gnu.org 2022-08-08 6:52 ` [Bug analyzer/106551] " rguenth at gcc dot gnu.org 2022-08-08 14:02 ` dmalcolm at gcc dot gnu.org 2022-08-09 7:48 ` [Bug analyzer/106551] [13 Regression] dup2 causes -fanalyzer " mir at gcc dot gnu.org 2022-08-11 16:21 ` cvs-commit at gcc dot gnu.org 2022-08-14 20:27 ` tlange at gcc dot gnu.org 2022-08-15 8:37 ` mir at gcc dot gnu.org 2022-08-15 16:52 ` cvs-commit at gcc dot gnu.org [this message] 2022-08-15 16:55 ` mir 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-106551-4-EZZZC20b53@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).