summaryrefslogtreecommitdiff
path: root/Tools/c-analyzer/cpython/_analyzer.py
Commit message (Collapse)AuthorAgeFilesLines
* gh-102033: Fix syntax error in `Tools/c-analyzer` (GH-102066)Nikita Sobolev2023-03-221-4/+0
| | | The easiest way to format strings with `{}` meaningful chars is via `%`.
* gh-90110: Update the c-analyzer Tool (gh-97695)Eric Snow2022-09-301-0/+4
| | | https://github.com/python/cpython/issues/90110
* gh-90110: Update the c-analyzer Tool (gh-96255)Eric Snow2022-08-251-0/+72
| | | Here we automatically ignore uses of _PyArg_Parser, "kwlist" arrays, and module/type defs. That way new uses don't trigger false positives in the c-analyzer check script.
* bpo-36876: Make sure the c-analyzer is checking all the source files.' ↵Eric Snow2022-02-101-1/+1
| | | | | (gh-31264) https://bugs.python.org/issue36876
* bpo-36876: Update the c-analyzer whitelist. (gh-31225)Eric Snow2022-02-081-0/+2
| | | | | This change adds variables that had been added since the last time the whitelist was updated. It also cleans up the list a little. https://bugs.python.org/issue36876
* bpo-36876: [c-analyzer tool] Tighten up the results and output. (GH-23431)Eric Snow2020-11-201-2/+2
| | | We also update the "ignored" file with a temporary list of all known globals.
* bpo-36876: Small adjustments to the C-analyzer tool. (GH-23045)Eric Snow2020-10-301-1/+6
| | | This is a little bit of clean-up, small fixes, and additional helpers prior to building an updated & accurate list of globals to eliminate.
* bpo-36876: Fix the C analyzer tool. (GH-22841)Eric Snow2020-10-221-0/+348
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