From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NUlG0-0002Un-E2 for qemu-devel@nongnu.org; Tue, 12 Jan 2010 13:14:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NUlFw-0002TZ-Oj for qemu-devel@nongnu.org; Tue, 12 Jan 2010 13:14:20 -0500 Received: from [199.232.76.173] (port=57065 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NUlFw-0002TR-IZ for qemu-devel@nongnu.org; Tue, 12 Jan 2010 13:14:16 -0500 Received: from mx1.redhat.com ([209.132.183.28]:6015) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NUlFv-0004bo-VP for qemu-devel@nongnu.org; Tue, 12 Jan 2010 13:14:16 -0500 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o0CIEEsY030730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 12 Jan 2010 13:14:14 -0500 Received: from localhost (vpn-232-126.phx2.redhat.com [10.3.232.126]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o0CIECEc006618 for ; Tue, 12 Jan 2010 13:14:13 -0500 Date: Tue, 12 Jan 2010 23:43:07 +0530 From: Amit Shah Message-ID: <20100112181307.GD19438@amit-x200.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] Static analysis using clang on the x86_64 target List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hello, Here's a run of the clang analyzer on qemu sources for the x86_64 target. See http://amitshah.fedorapeople.org/clang-output/2010-01-12-9/ for the results. There are a few results there which look dubious but a lot of the output can be useful to fix the bugs. What's nice about the tool is that the output is the source code annotated with the branch decisions that were taken to point out to the case where a bug would be triggered. Doing this for all the targets takes a really long time plus lots of disk space (I stopped the compile at 400M of clang output). If there's interest in this kind of result, I can post a link to the list every week or so. However, some bugs reported make it slightly less appealing as real bugs could get lost in the noise. For information on the clang static analyzer, see http://clang-analyzer.llvm.org/ Amit