From: "Дилян Палаузов" <dilyan.palauzov@aegee.org>
To: git@vger.kernel.org
Subject: git and the Clang Static Analyzer
Date: Sun, 7 May 2017 13:50:54 +0200 [thread overview]
Message-ID: <5696a8a3-0a17-18ac-8da4-4556586acee7@aegee.org> (raw)
Hello,
I compiled git/master using the clang 4.0 static analyzer with
scan-build ./configure --with-libpcre --with-openssl
scan-build make
and here are the results:
https://mail.aegee.org/dpa/scan-build-git-4fa66c85f11/
Please note, that the information is only about what gets actually
compiled, code disabled by #if .. #endif is not considered (e.g. when
determining whether a variable assignment is useless). There are
probably false-positives. However in case of e.g. builtin/notes.c:1018,
builtin/reset.c:294 or fast-import.c:2057 I consider the hints as justified.
This is for your information, I wouldn't have a problem if you ignore
the analysis. When you are worried about javascript, use lynx.
Regards
Дилян
next reply other threads:[~2017-05-07 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 11:50 Дилян Палаузов [this message]
2017-05-08 11:12 ` git and the Clang Static Analyzer Johannes Schindelin
2017-05-08 16:45 ` Lars Schneider
2017-05-08 19:26 ` Дилян Палаузов
2017-05-08 20:18 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5696a8a3-0a17-18ac-8da4-4556586acee7@aegee.org \
--to=dilyan.palauzov@aegee.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).