From: "Wiles, Roger Keith" <keith.wiles@windriver.com>
To: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: [dpdk-dev] Clang Scan build results
Date: Wed, 27 Aug 2014 15:13:43 +0000 [thread overview]
Message-ID: <AE564FD4-F0B0-4FC0-88F2-ABAB1844F9A5@windriver.com> (raw)
Hi Everyone,
I built dpdk with Clang and used the scan-build analyzer to produce a report. The report is about 13M in size so not very nice to send to the list. I decided to place the report on github.com if you want to see the results.
While running scan-build the build would fail, but I forced the build to continue using the scan-build option to get as much of the report as possible. I did not have time yet to understand why the build stopped and I hope to dig into it more later.
Running scan-build is pretty simple, so would be a nice test report if you wanted to add it to dpdk.org site and maintain its output for review. It would be nice to run once in a while to weed out any basic problems. We could run something like PC-Lint or Coverity, but they cost money :-)
Here is the link to my Pktgen-DPDK repos on github:
# git clone git://github.com/Pktgen/dpdk-scan-build-results.git
Let me know if you have any questions or suggestions.
Thanks
++Keith
Keith Wiles, Principal Technologist with CTO office, Wind River mobile 972-213-5533
next reply other threads:[~2014-08-27 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 15:13 Wiles, Roger Keith [this message]
2014-08-27 15:24 ` Jay Rolette
2014-08-27 15:52 ` Wiles, Roger Keith
2014-08-27 15:58 ` Jay Rolette
2014-08-27 16:09 ` Thomas Monjalon
2014-08-27 16:19 ` Wiles, Roger Keith
2014-08-27 17:02 ` Vincent JARDIN
2014-08-27 17:55 ` Julien Cretin
2014-08-28 3:00 ` Matthew Hall
2014-08-28 5:29 ` Wiles, Roger Keith
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=AE564FD4-F0B0-4FC0-88F2-ABAB1844F9A5@windriver.com \
--to=keith.wiles@windriver.com \
--cc=dev@dpdk.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).