DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Roger Keith" <keith.wiles@windriver.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Clang Scan build results
Date: Thu, 28 Aug 2014 05:29:36 +0000	[thread overview]
Message-ID: <E7AD442D-B1B1-4054-B36C-1FC2CBB802DC@windriver.com> (raw)
In-Reply-To: <20140828030025.GB12478@mhcomputing.net>

Hi Matthew,

On Aug 27, 2014, at 10:00 PM, Matthew Hall <mhall@mhcomputing.net> wrote:

> On Wed, Aug 27, 2014 at 03:13:43PM +0000, Wiles, Roger Keith wrote:
>> Hi Everyone,
> 
> Hi Keith,
> 
> For me the build failed with clang but I made a series of awful patches to get 
> it to compile... not sure if the clang failures could be related to your 
> scan-build failures. If it will help you I can provide you the patches I made 
> to get it to work on clang... they are not ready for the DPDK master branch 
> but it's really good to get safe output from scan-build.

I was able to get DPDK to build using target x86_64-native-linuxapp-clang without errors, but with scan-build it gave me errors that were not in the normal clang build. Was this the target system you were building or something else?
> 
>> 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 :-)
> 
> Not 100% true... you can run Coverity for free on open source if you are the 
> maintainer... given Intel, Wind River, and 6WIND all have some form of 
> maintainership authority over DPDK there should be a way to qualify via this 
> avenue.

Yes, it was pointer out to me that Coverity is free to open source via scan.coverity.com site, just have to register and get accepted.
> 
> Matthew.

Keith Wiles, Principal Technologist with CTO office, Wind River mobile 972-213-5533

      reply	other threads:[~2014-08-28  5:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 15:13 Wiles, Roger Keith
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 [this message]

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=E7AD442D-B1B1-4054-B36C-1FC2CBB802DC@windriver.com \
    --to=keith.wiles@windriver.com \
    --cc=dev@dpdk.org \
    --cc=mhall@mhcomputing.net \
    /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).