On Thu, 28 Aug 2025 15:17:47 GMT, Matthias Baesken <mbaes...@openjdk.org> wrote:
> Recent versions of GCC have a static code analyzer option (-fanalyzer) that > works quite well for C code (but it has still issues with C++). > This can be used to identify e.g. some leaks like memory leaks, double close, > use of uninitialized data etc. . > Some info about it : > > https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html > https://developers.redhat.com/articles/2023/05/31/improvements-static-analysis-gcc-13-compiler make/autoconf/jdk-options.m4 line 489: > 487: [ > 488: UTIL_ARG_ENABLE(NAME: static-analyzer, DEFAULT: false, RESULT: > STATIC_ANALYZER_ENABLED, > 489: DESC: [enable static analyzer], I think we can be more specific in the description, at as long as this option actually is GCC specific. Suggestion: DESC: [enable the GCC static analyzer], ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/26989#discussion_r2308003680
