[GSOC 2025] Interests in extending the static analysis pass(es): support for C++ or CPython API

[zzmic]

On Wed, Mar 19, 2025 at 10:46 PM zzmic <zzmicdev@gmail.com> wrote:
>
> Dear all,
>
>
> I hope you’ve been doing well!
>
> I’m Zhiwen, an undergraduate who is working towards his degree jointly in mathematics and computer science.
>
>
> I’m writing to express my interest in working on a medium-sized (or large-sized) project that, broadly speaking, extends the static-analysis pass(es). In particular, I’ve been dabbling between extending the analyzer’s support for C++ and extending the plugin to add checking for usage of the CPython API, such as reference counting. Both topics can be found in the [ideas list](https://gcc.gnu.org/wiki/SummerOfCode). Nevertheless, I haven’t yet settled down a fine-grained problem (in the scope of the aforementioned topics) to work on. For extending the analyzer’s support for C++, I was wondering if I should (or am expected to) curate a very specific proposition that may be generated from [the existing bugs](https://gcc.gnu.org/bugzilla/showdependencytree.cgi?id=97110) or something else (e.g., loosely coupling a batch of bugs that have a similar gist).
>
>
> To briefly introduce my background, I have gained previous experience in compilers, mainly through engineering compilers and interpreters in C++ and OCaml. One of the compiler projects I’ve been working on is [ccmic](https://github.com/zzmic/ccmic), a work-in-progress implementation of a C compiler (that supports a subset of the C programming language) written in C++. On top of that, I had and have been working on (1) an interpreter for a (quite simple/naive) object-oriented language that adheres to its syntax and small-step operational semantics and (2) compilers that can be thought of as transpilers that, for instance, compile scheme-like programs to C-like programs and compile C-like programs to RISC-V assembly. Furthermore, I’ve some experience in contributing to open-source projects, such as [p4c](https://github.com/p4lang/p4c), although the [PRs I made](https://github.com/p4lang/p4c/issues?q=state%3Aclosed%20is%3Apr%20author%3A%40me) are not game-changing and are definitely not to the extent of a GSoC project.

I'm sorry that the link that I attached with "PRs I made" doesn’t (and
won’t) work as intended. Just in case any of the message reviewers are
interested, the following link should point to the right place:
https://github.com/p4lang/p4c/pulls?q=state%3Aclosed+is%3Apr+author%3Azzmic.

> Thanks for your patience in reading this perhaps long-winded message, and please feel absolutely free to make any comments or suggestions.
>
>
> Best regards,
> Zhiwen