Re: GSOC 2023 Contribution Request

[Patrick Palka <ppalka@redhat.com>]

Hi Kritika,

On Wed, Feb 22, 2023 at 6:49 AM Kritika Rag via Gcc <gcc@gcc.gnu.org> wrote:
>
> Hello Everyone!
>
> I’m Kritika Rag, a Computer Science pre-final year undergraduate
> student from India. I’m quite passionate about web development and
> competitive programming and now I’m looking forward to contributing to
> open-source projects. I believe that GSOC 2023 would provide me with
> the best way to start my open-source contribution journey. Since I’m a
> competitive programmer, I have excellent command over Data Structures
> & Algorithms and my primary language is C++, so C++ and GCC are
> something that I use daily, therefore I would love to make my
> contributions to GCC projects. I sincerely hope that this community
> will provide me with the opportunity to do so and to work alongside
> them.

Great, thanks for your interest in contributing to GCC, and welcome!

>
>
> I’m proficient in various coding languages like C/C++, HTML, CSS,
> JavaScript, React, and Python, and have experimented with Git, Linux,
> APIs, etc. I have also been fortunate enough to secure 3 internships,
> 2 as a DSA problem setter and 1 as a research intern. I have also
> participated in a few open-source programs like Hack October Fest 2022
> and GWoC 2022 and contributed to web development and data science
> projects.
>
> I had been checking up on recent project proposals listed in GCC wiki
> for the past 3 weeks and was interested in working either on the
> project which aims to improve the utility routine library used by GCC
> or related to Bug Patrol especially analyzing failing test cases (this
> was present over the site a while ago but now I can't see it anywhere)
> so I just wanted to ask can I choose it as my GSoC 2023 project? If
> yes can anyone guide me to whom to connect to discuss it?
>
> And if I can't work on the above ideas then I have also gone through
> the selected project ideas and want to work on the project "Implement
> comp built-in traits for the standard library traits" so would be
> grateful if anyone could guide me here also.

I can't speak about the other projects, but I'm listed as the mentor
for the built-in C++ trait project idea.

On the frontend side most of the existing built-in traits are tabulated in
gcc/cp/cp-trait.def, and their logic is defined in finish_trait_type
or finish_trait_expr in gcc/cp/semantics.cc[2], and on library side the traits
are conditionally used in the standard type trait definitions in
libstdc++, e.g. std::remove_cv[3].

Take a look at the following commits that define (and add tests for)
the built-in traits __remove_cv, __remove_reference and __remove_cvref
and subsequently use them in libstdc++. Note that this first commit
predates the new gcc/cp/cp-trait.def file which streamlined much of
the boilerplate of adding a new built-in trait.  In the new approach
(that you would be using), only the semantics.cc change (which defines
their logic) would be needed, alongside additions to cp-trait.def to
declare each trait.
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9ca147154074a0de548138b4e73477e94903a855
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=6ddbbbffbb5759a6c1d56c191364a6bd021f733e

If you haven't already I'd recommend going through the GCC for new
contributors guide
https://gcc-newbies-guide.readthedocs.io/en/latest/index.html which
goes through checking out, building and debugging GCC.
Let me know if you have any questions :)

[1]: https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/cp/cp-trait.def
[2]: https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/cp/semantics.cc;h=79b7cc72f212cef780a3eea65af2b883bb4ec3c8;hb=HEAD#l12102
[3]: https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libstdc%2B%2B-v3/include/std/type_traits;h=2bd607a8b8ff52aba6fd205ab1af2bc4b92f78d0;hb=HEAD#l1539


>
> Thank you so much and I hope to hear from you soon.
>