[all-commits] [llvm/llvm-project] b98a59: [clang][analyzer] Move `security.cert.env.InvalidP...

[Endre Fülöp via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: b98a594977f25e555822e5ceef457f69c73cce45
      https://github.com/llvm/llvm-project/commit/b98a594977f25e555822e5ceef457f69c73cce45
  Author: Endre Fülöp <endre.fulop at sigmatechnology.com>
  Date:   2023-11-24 (Fri, 24 Nov 2023)

  Changed paths:
    M clang/docs/analyzer/checkers.rst
    M clang/include/clang/StaticAnalyzer/Checkers/Checkers.td
    M clang/test/Analysis/analyzer-config.c
    M clang/test/Analysis/cert/env31-c.c
    M clang/test/Analysis/cert/env34-c-cert-examples.c
    M clang/test/Analysis/cert/env34-c.c
    M clang/test/Analysis/invalid-ptr-checker.c

  Log Message:
  -----------
  [clang][analyzer] Move `security.cert.env.InvalidPtr` out of `alpha` (#71912)

Thanks to recent improvements in #67663, InvalidPtr checker does not
emit any false positives on the following OS projects: memcached, tmux,
curl, twin, vim, openssl, sqlite, ffmpeg, postgres, tinyxml2, libwebm,
xerces, bitcoin, protobuf, qtbase, contour, acid, openrct2. (Before the
changes mentioned above, there were 27 reports, catching the `getenv`
invalidates previous `getenv` results cases. That strict behaviour is
disabled by default)