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 7006D385842B; Fri, 11 Nov 2022 16:55:41 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7006D385842B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1668185741;
	bh=gWrAS2wFaY6pdp3QYBk5kpzWxfHHZYJcOHcy8z/hGQM=;
	h=From:To:Subject:Date:From;
	b=sYMpNch/WaItlgm76yEVTmvHES4ifdKZE06w9s4U4tEmx7gXAjct0og7A8+6pX2iX
	 bMxeuiqF7tY6GyB90f40TtMQLtAOAJeFwoPl6Tu+LTOwlQCw/ui0zkIISHlVDgFeF4
	 kFw3jgFBMY17p3lbX0rjDSt0COJxoO9ycWvkFmQU=
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/107646] New: RFE: can we reimplement
 gcc-python-plugin's cpychecker as a -fanalyzer plugin?
Date: Fri, 11 Nov 2022 16:55:41 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-107646-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=3D107646

            Bug ID: 107646
           Summary: RFE: can we reimplement gcc-python-plugin's cpychecker
                    as a -fanalyzer plugin?
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: dmalcolm at gcc dot gnu.org
  Target Milestone: ---

My gcc-python-plugin implements a crude static analysis of CPython code, us=
ing
symbolic execution in a manner similar to how -fanalyzer works, but it's be=
en
bitrotting for years, and is slow (being written in Python itself):
  https://gcc-python-plugin.readthedocs.io/en/latest/cpychecker.html

I *think* this could now be reimplemented as a plugin to GCC's -fanalyzer (=
in
C++), where -fanalyzer provides most of the framework needed, and we'd most=
ly
just need to write the CPython-specific parts.

It would make an interesting GSoC project (albeit perhaps a challenging one=
).=