Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpo-36876: Fix the C analyzer tool. #22841

Conversation

ericsnowcurrently
Copy link
Member

@ericsnowcurrently ericsnowcurrently commented Oct 21, 2020

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 ~35 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

@pablogsal
Copy link
Member

I would recommend checking with the buildbot label before merging as some of the refleaks were reported previously with the old analyzer (although most were false positives).

@ericsnowcurrently
Copy link
Member Author

I would recommend checking with the buildbot label before merging as some of the refleaks were reported previously with the old analyzer (although most were false positives).

FWIW, this PR removes all the tool's tests, except for the one we care about (and that one is currently disabled). So refleaks shouldn't be a problem. 😄

@ericsnowcurrently ericsnowcurrently merged commit 345cd37 into python:master Oct 23, 2020
@ericsnowcurrently ericsnowcurrently deleted the globalss-c-analyzer-total-rewrite branch October 23, 2020 00:42
adorilson pushed a commit to adorilson/cpython that referenced this pull request Mar 13, 2021
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants