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/106298] RFE: analyzer handling of dup, dup2, and dup3 Date: Tue, 02 Aug 2022 16:54:37 +0000 [thread overview] Message-ID: <bug-106298-4-ptyW1qIV64@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106298-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106298 --- Comment #3 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:6a11f2d974a912aaaedb0ce32cdfde10193003cd commit r13-1936-g6a11f2d974a912aaaedb0ce32cdfde10193003cd Author: Immad Mir <mirimmad@outlook.com> Date: Tue Aug 2 22:22:07 2022 +0530 analyzer: support for creat, dup, dup2 and dup3 [PR106298] This patch extends the state machine in sm-fd.cc to support creat, dup, dup2 and dup3 functions. Lightly tested on x86_64 Linux. gcc/analyzer/ChangeLog: PR analyzer/106298 * sm-fd.cc (fd_state_machine::on_open): Add creat, dup, dup2 and dup3 functions. (enum dup): New. (fd_state_machine::valid_to_unchecked_state): New. (fd_state_machine::on_creat): New. (fd_state_machine::on_dup): New. gcc/testsuite/ChangeLog: PR analyzer/106298 * gcc.dg/analyzer/fd-1.c: Add tests for 'creat'. * gcc.dg/analyzer/fd-2.c: Likewise. * gcc.dg/analyzer/fd-4.c: Likewise. * gcc.dg/analyzer/fd-dup-1.c: New tests. Signed-off-by: Immad Mir <mirimmad@outlook.com>
next prev parent reply other threads:[~2022-08-02 16:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-14 14:42 [Bug analyzer/106298] New: " dmalcolm at gcc dot gnu.org 2022-07-14 19:27 ` [Bug analyzer/106298] " egallager at gcc dot gnu.org 2022-07-27 17:56 ` dmalcolm at gcc dot gnu.org 2022-08-02 16:54 ` cvs-commit at gcc dot gnu.org [this message] 2022-08-02 18:03 ` 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-106298-4-ptyW1qIV64@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).