Hello, I'm writing an application for GSoC, and would like a little feedback.
Application: This application is about enabling exception handling control flow in the static analyzer. Exception support is integral to C++ support, as most of the standard library uses exceptions to communicate errors. Background: I am a sophomore student at San Jose State University, and have been messing around with compilers lately. I've previously modified GCC to support C++ exception handling and the standard library on AVR. I am quite familiar with C and C++. I've mostly had experience with modifying the library parts of GCC (libgcc), with a little bit of experience with the back end GIMPLE emission (as a part of fixing GCC exception handling data emission on AVR). I was first drawn to GCC mostly out of a practical requirement (AVR support), and now I have future projects I would like to do in GCC. Before that though, I would like to learn more thoroughly about the typical GCC development process. For that reason, I am submitting a proposal through GSoC to GCC. Expected outcome: A patch resolving bug 97111, enabling support for exception handling in the analyzer. This issue also probably blocks 94355 because operator new can throw exceptions, and 110578 because dynamic cast on references can throw. There are also probably other checks on exceptions that may be valuable. Timeline: Weeks 1 - 4: Investigate current state of exception support in GCC. I've already built GCC, so it's just a matter of dumping GIMPLE and the exploded graph. After that, begin work on minimum viable product. Weeks 5 - 8: Continue work on minimum viable product. Weeks 8 - 12: Hopefully the minimum viable product is done at this point. Document appropriately, refactor patches to be more clear, add additional checks if there is time.
