GSoC: want to take part in `Extend the static analysis pass for CPython Extension`

[Sun Steven <StevenSun2021@hotmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

Hello,

I want to take part in this project.

b. Write a plugin to add checking for usage of the CPython API (e.g. reference-counting); see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107646


I know the deadline is arriving, but this idea just came to me now.

Self-intro:
I am a fan of C++, and have expertise in writing low-latency codes. I previously worked at a high-frequency trading company, mainly writing C++ and Python on Linux.

Familiarity with GCC:
I get an overall idea of how the compiler works. I have debugged several GCC c++ frontend bugs. (eg. 108218,  99686, 99019,...) But I only checked the c++ frontend codes in detail, not the middle or backend codes. I have the ability to work with large codebases.

Familiarity with CPython:
I use a lot of CPython. Recently, I am contributing to the CPython interpreter on PEP 701 (mainly on the parser, which I am familiar with)


I have always been wanting to contribute major changes to GCC, but just don't know if that project exists. I understand how middle-end works, but never really interact with the GIMPLE. This project allows me to take a real look at how GCC's middle end works.

I want to know if anyone was already on this project. I would prefer a large-sized object (350hrs).

If b. was already taken, I also accept a. and c. By the way, I don't really care about the GSoC. If we miss the deadline, we can still push forward this project without the support of GSoC, as long as I get coached.