On Sun, Aug 11, 2013 at 6:56 AM, Roland Mainz <[email protected]> wrote: > Attached (as "clang_scan_build_ast_ksh_20130807_suse123_log001.txt") > is the build log containing the warnings of a "scan-build" (see > http://clang-analyzer.llvm.org/scan-build.html) run of clang's static > analyser. Note that the warnings are _not_ compiler warnings/errors... > these are warnins created while doing a static analysis of the code... > which seems to reveal some *SERIOUS* issues in the code (I say "seems" > since there are likely lots of "false positives" in the code... may of > them caused by the custom memory allocators used by libast which > "clang" doesn't recognises as such... ;-/ ) but likely there are a > couple of real big problems, too. > And there are often "gems" like this one (dead code): > -- snip -- > src/cmd/msggen/msgcvt.c:686:2: warning: Value stored to 'argv' is never read > argv += opt_info.index; > ^ ~~~~~~~~~~~~~~ > -- snip -- > > The log was created with the following command-line: > -- snip -- > $ (export CC='/usr/bin/clang -std=gnu1x -g -fno-omit-frame-pointer > -fno-optimize-sibling-calls -Wno-parentheses > -Wno-logical-op-parentheses -Wno-unused' LD="$CC" CCFLAGS="-g"; time > scan-build ksh ./bin/package make PACKAGE_OPTIONS='map-libc' 2>&1 | > tee -a 'clang_scan_build_ast_ksh_20130807_suse123_log001.txt' > -- snip -- > > Please read the logs... some examples of "false positives" would be > nice that I can try to fix some bugs in "clang" ... and likely some in > AST, too... :-)
Erm... has anyone looked at the logs yet ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [email protected] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
