=?utf-8?q?Donát?= Nagy <donat.n...@ericsson.com> Message-ID: In-Reply-To: <llvm.org/llvm/llvm-project/pull/103...@github.com>
================ @@ -1039,10 +1039,6 @@ def ArrayBoundCheckerV2 : Checker<"ArrayBoundV2">, HelpText<"Warn about buffer overflows (newer checker)">, Documentation<HasDocumentation>; -def MallocOverflowSecurityChecker : Checker<"MallocOverflow">, ---------------- steakhal wrote: I'm not sure it's necessity. They could fork it and revert this change if they really wanted. I doubt that would be the case. @NagyDonat If you really want to make this a backward-compatible change, you could add a new bool checker option like `"enable-despite-this-checker-is-deprecated-and-will-be-removed"`, and leave the checker - until we branch off for clang-20 in mid January. But personally, I wouldn't want to wait for 4 months for removing an alpha checker. We could reconsider this and clarify the policies if users complain that alpha checkers were removed without any notice. https://github.com/llvm/llvm-project/pull/103059 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
