summaryrefslogtreecommitdiffstats
path: root/Tools/c-analyzer/c_parser/preprocessor
Commit message (Collapse)AuthorAgeFilesLines
* gh-90110: Fix the c-analyzer Tool (#102483)Eric Snow2023-03-071-1/+2
| | | | | | | Some incompatible changes had gone in, and the "ignore" lists weren't properly undated. This change fixes that. It's necessary prior to enabling test_check_c_globals, which I hope to do soon. Note that this does include moving last_resort_memory_error to PyInterpreterState. https://github.com/python/cpython/issues/90110
* gh-90110: Fix the c-analyzer Tool (gh-96731)Eric Snow2022-09-124-35/+218
| | | | | | | This includes: * update the whitelists * fixes so we can stop ignoring some of the files * ensure Include/cpython/*.h get analyzed
* gh-85454: Remove distutils.ccompiler from Tools/c-analyzer (GH-95171)Dong-hee Na2022-07-251-2/+12
|
* bpo-45952: Get the C analyzer tool working again. (gh-29882)Eric Snow2021-12-011-1/+1
| | | | | There wasn't much that needed to be done. Mostly it was just a few new files that got added. https://bugs.python.org/issue45952
* Fix typos in the Tools directory (GH-28769)Christian Clauss2021-10-061-2/+2
| | | | | | | Like #28744 but for the Tools directory. [skip issue] Opening a related issue is pending python/psf-infra-meta#130 Automerge-Triggered-By: GH:pablogsal
* bpo-44854: Remove trailing whitespaces (GH-27689)Serhiy Storchaka2021-08-091-1/+1
|
* bpo-36876: [c-analyzer tool] Add a "capi" subcommand to the c-analyzer tool. ↵Eric Snow2020-12-241-2/+3
| | | | | | | (gh-23918) This will help identify which C-API items will need to be updated for subinterpreter support. https://bugs.python.org/issue36876
* bpo-36876: Fix the C analyzer tool. (GH-22841)Eric Snow2020-10-236-0/+815
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