public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Briand <atb8888@comcast.net>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: GSoC Static Analysis
Date: Wed, 25 Mar 2020 15:36:28 -0700	[thread overview]
Message-ID: <20200325223628.RJMxBphxMLdK5G4wpDeq7iUx9YjvEguRgWLERbmK9T8@z> (raw)

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. 

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.

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.

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.

Thanks,

Andrew Briand

             reply	other threads:[~2020-03-25 22:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 22:36 Andrew Briand [this message]
2020-03-25 22:36 Andrew Briand
2020-03-25 22:36 Andrew Briand
     [not found] <20200325223732.74127385E01C@sourceware.org>
2020-03-27  1:42 ` David Malcolm
2020-03-27  9:01 ` Jonathan Wakely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200325223628.RJMxBphxMLdK5G4wpDeq7iUx9YjvEguRgWLERbmK9T8@z \
    --to=atb8888@comcast.net \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).