Staging
v0.5.1
https://github.com/python/cpython
Revision 345cd37abe324ad4f60f80e2c3133b8849e54e9b authored by Eric Snow on 23 October 2020, 00:42:51 UTC, committed by GitHub on 23 October 2020, 00:42:51 UTC
The original tool wasn't working right and it was simpler to create a new one, partially re-using some of the old code. At this point the tool runs properly on the master. (Try: ./python Tools/c-analyzer/c-analyzer.py analyze.)  It take ~40 seconds on my machine to analyze the full CPython code base.

Note that we'll need to iron out some OS-specific stuff (e.g. preprocessor). We're okay though since this tool isn't used yet in our workflow. We will also need to verify the analysis results in detail before activating the check in CI, though I'm pretty sure it's close.

https://bugs.python.org/issue36876
1 parent ec388cf
History
Tip revision: 345cd37abe324ad4f60f80e2c3133b8849e54e9b authored by Eric Snow on 23 October 2020, 00:42:51 UTC
bpo-36876: Fix the C analyzer tool. (GH-22841)
Tip revision: 345cd37
File Mode Size
NEWS.d
ACKS -rw-r--r-- 28.2 KB
HISTORY -rw-r--r-- 1.3 MB
Porting -rw-r--r-- 63 bytes
README -rw-r--r-- 1.4 KB
README.AIX -rw-r--r-- 4.7 KB
README.coverity -rw-r--r-- 845 bytes
README.valgrind -rw-r--r-- 4.8 KB
SpecialBuilds.txt -rw-r--r-- 7.7 KB
coverity_model.c -rw-r--r-- 4.0 KB
gdbinit -rw-r--r-- 4.8 KB
indent.pro -rw-r--r-- 557 bytes
python-config.in -rw-r--r-- 2.0 KB
python-config.sh.in -rw-r--r-- 2.9 KB
python-embed.pc.in -rw-r--r-- 310 bytes
python-wing3.wpr -rwxr-xr-x 555 bytes
python-wing4.wpr -rwxr-xr-x 835 bytes
python-wing5.wpr -rwxr-xr-x 835 bytes
python.man -rw-r--r-- 17.8 KB
python.pc.in -rw-r--r-- 268 bytes
requirements-test.txt -rw-r--r-- 15 bytes
svnmap.txt -rw-r--r-- 4.1 MB
valgrind-python.supp -rw-r--r-- 8.6 KB
vgrindefs -rw-r--r-- 500 bytes

README

back to top