public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/106003] RFE: -fanalyzer could complain about misuse of file-descriptors
Date: Sat, 23 Jul 2022 17:40:56 +0000	[thread overview]
Message-ID: <bug-106003-4-DqeahmIB4d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106003-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106003

--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
I don't think we were tracking the RFE for this in bugzilla, so just a note
that Immad had now committed his patch for the three new attributes for
functions that make use of file descriptors:
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=f8e6e2c046e1015697356ee7079fb39e0cb6add5

I've also added a link to this to https://gcc.gnu.org/wiki/StaticAnalyzer

Thanks Immad

  parent reply	other threads:[~2022-07-23 17:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 15:21 [Bug analyzer/106003] New: " dmalcolm at gcc dot gnu.org
2022-06-16 15:30 ` [Bug analyzer/106003] " dmalcolm at gcc dot gnu.org
2022-06-19 12:27 ` mir at gcc dot gnu.org
2022-07-02 16:45 ` cvs-commit at gcc dot gnu.org
2022-07-04  8:50 ` marxin at gcc dot gnu.org
2022-07-04 14:08 ` marxin at gcc dot gnu.org
2022-07-04 14:16 ` mir at gcc dot gnu.org
2022-07-23 17:40 ` dmalcolm at gcc dot gnu.org [this message]
2022-07-27 13:58 ` mir at gcc dot gnu.org
2022-08-02 18:03 ` mir at gcc dot gnu.org
2022-10-24 21:00 ` dmalcolm at gcc dot gnu.org
2022-11-03 14:58 ` dmalcolm at gcc dot gnu.org
2022-11-15 19:11 ` dmalcolm at gcc dot gnu.org
2022-11-15 19:13 ` dmalcolm at gcc dot gnu.org
2023-01-10 16:13 ` 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-106003-4-DqeahmIB4d@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).