From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 8517A3858C52; Wed, 18 Jan 2023 16:17:06 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8517A3858C52
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1674058626;
	bh=PDNc154d62a72BEPC9gNsplyacAvl2lO9lO94GD4B3o=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=eMOLe9zlQPfW/JSUdgqDQqFfcQ6ODnA46KDz99rLiY/3T3+Qk77WkI11aFy/I1Vg5
	 2FLZlFEhDXOfbZ5gLdVv1Pr3KYWbajkuQ/YB8omD+5acx/Upm2WLQMj8FSf1AL2Jgl
	 0qLd3mtIidgH0MVI9Fk2LfBWvOPWjHXQ/DtZocAk=
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/102471] RFE: add support to analyzer testsuite for
 running SAMATE/SARD tests (e.g. Juliet Test Suite)
Date: Wed, 18 Jan 2023 16:17:05 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-102471-4-1zvH1tfQ1Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-102471-4@http.gcc.gnu.org/bugzilla/>
References: <bug-102471-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102471

--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
I've created
  https://github.com/davidmalcolm/gcc-analyzer-integration-tests
which builds Juliet plus various real-world C projects with a candidate bui=
ld
of GCC with -fanalyzer and captures the diagnostics in SARIF format.

https://github.com/microsoft/sarif-tools has a command for comparing SARIF
files (or pairs of directories full of SARIF files) which is what I'm curre=
ntly
using to compare diagnostics emitted before/after a candidate GCC patch.

I'm working through the diagnostics seen with GCC trunk's -fanalyzer,
classifying them into true vs false positives and will probably write my own
comparison script to show the effect of a GCC patch on false vs true positi=
ves.=