From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 754195946 for ; Thu, 28 Aug 2014 04:56:19 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 23F0C80C764; Wed, 27 Aug 2014 20:00:25 -0700 (PDT) Date: Wed, 27 Aug 2014 20:00:25 -0700 From: Matthew Hall To: "Wiles, Roger Keith" Message-ID: <20140828030025.GB12478@mhcomputing.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "" Subject: Re: [dpdk-dev] Clang Scan build results X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2014 02:56:20 -0000 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. > 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. Matthew.