[analyzer][docs] Add clang-19 release notes for CSA #97418
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
steakhal
added
documentation
clang
|
@llvm/pr-subscribers-clang-static-analyzer-1 @llvm/pr-subscribers-clang Author: Balazs Benics (steakhal) ChangesThe day is coming for creating the release branch for clang-19, scheduled for the 23rd of July. After this is merged, let's try to keep the ReleaseNotes in sync with the changes. After dropping the two unrelated entries, the release notes would look like this: Full diff: https://github.com/llvm/llvm-project/pull/97418.diff 1 Files Affected:
diff --git a/clang/docs/ReleaseNotes.rst b/clang/docs/ReleaseNotes.rst
index 9741730604441..1d9f8b40419ec 100644
--- a/clang/docs/ReleaseNotes.rst
+++ b/clang/docs/ReleaseNotes.rst
@@ -1151,32 +1151,108 @@ libclang
Static Analyzer
---------------
+New features
+^^^^^^^^^^^^
+
+- The attribute ``[[clang::suppress]]`` can now be applied to declarations.
+ (#GH80371)
+
+- Support C++23 static operator calls. (#GH84972)
+
+Crash and bug fixes
+^^^^^^^^^^^^^^^^^^^
+
- Fixed crashing on loops if the loop variable was declared in switch blocks
but not under any case blocks if ``unroll-loops=true`` analyzer config is
set. (#GH68819)
-- Support C++23 static operator calls. (#GH84972)
+
- Fixed a crash in ``security.cert.env.InvalidPtr`` checker when accidentally
- matched user-defined ``strerror`` and similar library functions. (GH#88181)
-- Fixed a crash when storing through an address that refers to the address of
- a label. (GH#89185)
+ matched user-defined ``strerror`` and similar library functions. (#GH88181)
-New features
-^^^^^^^^^^^^
+- Fixed a crash when storing through an address that refers to the address of
+ a label. (#GH89185)
-Crash and bug fixes
-^^^^^^^^^^^^^^^^^^^
+- Z3 crosschecking (aka. Z3 refutation) is now bounded, and can't consume
+ more total time than the eymbolic execution itself. (#GH97298)
Improvements
^^^^^^^^^^^^
+- Many improvements for the ``unix.Stream`` checker, by modeling more functions
+ and improving overall diagnostic quality.
+
+ `Documentation <https://clang.llvm.org/docs/analyzer/checkers.html#unix-stream-c>`__.
+
+- Microsoft ``__assume`` is now recognized as ``__builtin_assume``. (#GH80456)
+
+- ``unix.Malloc`` suppresses false-positives involving ``std::atomic`` values.
+ (#GH90918)
+
+- Improved modeling of ``execv``, ``execvp``, ``popen``, ``pclose`` and
+ ``realpath`` in the ``unix.StdCLibraryFunctions`` checker.
+ `Documentation <https://clang.llvm.org/docs/analyzer/checkers.html#unix-stdclibraryfunctions-c>`__.
+
+- Many improvements were made to make function matching more accurate,
+ leading to fewer false positives.
+
+- Small improvements to ``optin.portability.UnixAPI``, ``core.VLASize``,
+ ``unix.BlockInCriticalSection``, ``core.NullDereference``, ``unix.Malloc``,
+ ``alpha.deadcode.UnreachableCode``, ``alpha.core.PointerSub``,
+ ``alpha.security.ArrayBoundV2`` checkers.
+
+- Many ``alpha.WebKit.*`` improvements.
+
- Support importing C++20 modules in clang-repl.
- Added support for ``TypeLoc::dump()`` for easier debugging, and improved
textual and JSON dumping for various ``TypeLoc``-related nodes.
+New checkers or configuration values
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- Added a new checker ``security.SetgidSetuidOrder`` which checks correct
+ usages of ``setuid`` and ``setguid`` call sequences to drop superuser
+ privileges. (#GH91445)
+ `Documentation <https://clang.llvm.org/docs/analyzer/checkers.html#security-setgidsetuidorder-c>`__.
+
+- Added a new checker ``optin.taint.TaintedAlloc`` which reports for passing
+ tainted ``size`` parameter to ``malloc``, ``calloc``, ``realloc``, ``alloca``
+ or to the C++ new operator. (#GH92420)
+ `Documentation <https://clang.llvm.org/docs/analyzer/checkers.html#optin-taint-taintedalloc-c-c>`__.
+
+- The ``unix.Stream`` gained the ``pedantic`` configuration option to warn for
+ not checking the return value of write operations for success or failure.
+ Enabling this may introduce a signifficant amount of false-positives.
+ (#GH87322)
+ `Documentation <https://clang.llvm.org/docs/analyzer/checkers.html#unix-stream-c>`__.
+
+- The configuration value ``ModelPosix`` now defaults to ``true`` in the
+ ``unix.StdCLibraryFunctions`` checker. (#GH80457)
+ `Documentation <https://clang.llvm.org/docs/analyzer/checkers.html#unix-stdclibraryfunctions-c>`__.
+
Moved checkers
^^^^^^^^^^^^^^
+- Moved ``alpha.cplusplus.ArrayDelete`` out of the ``alpha`` package
+ to ``cplusplus.ArrayDelete``. (#GH83985)
+ `Documentation <https://clang.llvm.org/docs/analyzer/checkers.html#cplusplus-arraydelete-c>`__.
+
+- Moved ``alpha.unix.Stream`` out of the ``alpha`` package to
+ ``unix.Stream``. (#GH89247)
+ `Documentation <https://clang.llvm.org/docs/analyzer/checkers.html#unix-stream-c>`__.
+
+- Moved ``alpha.unix.BlockInCriticalSection`` out of the ``alpha`` package to
+ ``unix.BlockInCriticalSection``. (#GH93815)
+ `Documentation <https://clang.llvm.org/docs/analyzer/checkers.html#unix-blockincriticalsection-c-c>`__.
+
+- Moved ``alpha.security.cert.pos.34c`` out of the ``alpha`` package to
+ ``security.PutenvStackArray``. (#GH92424, #GH93815)
+ `Documentation <https://clang.llvm.org/docs/analyzer/checkers.html#security-putenvstackarray-c>`__.
+
+- Moved ``alpha.core.SizeofPtr`` into ``clang-tidy``
+ ``bugprone-sizeof-expression``. (#GH95118, #GH94356)
+ `Documentation <https://clang.llvm.org/extra/clang-tidy/checks/bugprone/sizeof-expression.html>`__.
+
.. _release-notes-sanitizers:
Sanitizers
|
|
Ping. |
|
Small note, the screenshot has the "improvements" part, but I did not find that in the actual PR. |
|
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/123/builds/1524 Here is the relevant piece of the build log for the reference: |
aaryanshukla
pushed a commit
to aaryanshukla/llvm-project
that referenced
this pull request
Jul 14, 2024
The day is coming for creating the release branch for clang-19, [scheduled](https://discourse.llvm.org/t/llvm-19-release-schedule-and-planning/79828) for the 23rd of July. Let's start syncing the ReleaseNotes, and be proud of what we achieved since clang-18. After this is merged, let's try to keep the ReleaseNotes in sync with the changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The day is coming for creating the release branch for clang-19, scheduled for the 23rd of July.
Let's start syncing the ReleaseNotes, and be proud of what we achieved since clang-18.
After this is merged, let's try to keep the ReleaseNotes in sync with the changes.
After dropping the two unrelated entries, the release notes would look like this:
