[cfe-dev] GSOC Static Analyzer Proposal
dblaikie at gmail.com
Sun Apr 14 23:31:49 PDT 2013
On Tue, Apr 9, 2013 at 8:51 PM, Adam Schnitzer <adamschn at umich.edu> wrote:
> Hello All,
> I am planning on proposing a project for Google Summer of Code this summer,
> and would like to get your feedback before I write up a formal proposal.
> I would like to work on improving support for C++ in the static analyzer.
> Specifically, I think it would be valuable to improve the checkers for
> undefined behavior including those already suggested.
> Also, I think it would be helpful to extend the static analyzer to check for
> stylistic violations. For example, projects like LLVM have suggestions like,
> "Don't use else after a return". These warnings would often be noisy, and
> project dependent, so it would be useful to make those options configurable
> and suppressible.
Many stylistic issues wouldn't likely need the full power of the Clang
Static Analyzer. I suspect it would be better to factor such checks
out of the SA and then have the SA as one (allbeit expensive)
configurable check alongside many others. But I could be wrong - not
sure how lightweight the SA can be if it's doing simple things.
> I am also interested in implementing several of the optimization checkers.
> Specifically, it would be valuable to have warnings about postfix increment
> and pass by value give an idea of how large the object being copied is.
Aside: pass by value is actually surprisingly /good/ in the presence
of move semantics/swaptimizations. But those could be detected.
> I would be very interested to hear your feedback, specifically, if you think
> this project would be valuable.
> Thank You,
> Adam Schnitzer
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
More information about the cfe-dev