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

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mir at gcc dot gnu.org

--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Immad Mir has spent this summer working on adding support for tracking file
descriptors to -fanalyzer for GCC 13 (as part of GSoC 2022), and he's made a
lot of progress; see:
  *
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=97baacba963c06e3d0e33cde04e7e687671e60e7
which adds five new warnings, relating to misuses of file descriptors:
    -Wanalyzer-fd-access-mode-mismatch
    -Wanalyzer-fd-double-close
    -Wanalyzer-fd-leak
    -Wanalyzer-fd-use-after-close
    -Wanalyzer-fd-use-without-check 
and specialcases the analyzer's handling of open, close, read, and write.

  *
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=f8e6e2c046e1015697356ee7079fb39e0cb6add5
which adds three new function attributes for int parameters that refer to file
descriptors

  *
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=6a11f2d974a912aaaedb0ce32cdfde10193003cd
which specialcases the analyzer's handling of creat, dup, dup2 and dup3.

See also:
  https://gcc.gnu.org/bugzilla/showdependencytree.cgi?id=106003&hide_resolved=0
which I hope covers the rest of what you're asking for.

Are we missing anything?

Reply via email to