On Wed, 2020-03-25 at 15:36 -0700, Andrew Briand via Gcc wrote:
> Hello,
> 
> I am an undergrad interested in extending GCC’s static analysis pass
> for GSoC 2020. In particular, I’m interested in adding C++ support. 

Hi Andrew, thanks for your interest in the project.

> The selected project ideas list mentions adding new/delete checking
> and exception checking. The features that immediately come to my mind
> would be checking for undeleted allocations, mixing delete and
> delete[], double deletion (it seems the current static analyzer
> already checks for double free), and uncaught exceptions.

This sounds like a good list.  The analyzer currently ignores parts of
GCC's IR relating to exceptions, so properly supporting them will
require some new code.

> What would the expected scope of this project be? All of these
> features sound interesting to me, but I have no idea if doing all of
> them would be feasible within GSoC.

I kept the scope of the proposal quite broad, as there's plenty of work
to be done on the analyzer.

Several people have expressed an interest in the project (and, indeed
in the C++ part of it).  There may be room for more than one analyzer-
related project if we carve things out appropriately.  I think
realistically I don't have the bandwidth for more than two people (and
even that may be pushing it, especially given the disruption we're all
facing).

> For information about my experience, I have about a year and a half
> of C++ experience (about nine months in a large code base), have
> written a few toy compilers in the past, and will soon be starting to
> take a formal course about compilers at my university.

Sounds good.

A good next step for those interested in the project might be to try
compiling the analyzer from source.

David

Reply via email to