Welcome GCC GSoC 2023 participants
Hello, I am pleased to announce that again we will have six contributors working on GCC as part of their Google Summer of Code (GSoC) projects in 2023! In no particular order: - Benjamin Priour will be "Extending gcc -fanalyzer C++ support for self-analysis." and the project will be mentored by David Malcolm. - Eric Feng will be working on "Porting cpychecker to a -fanalyzer plugin" and his mentor will also be David Malcolm. - Ken Matsui will look into C++ and in particular will "Implement compiler built-in traits for the standard library traits." This project will be mentored by Patrick Palka. - Muhammad Mahad will be "Improving user errors" in our new Rust front-end and will be mentored by Arthur Cohen and Philip Herron. - Raiki Tamura has succeeded with a project to "Support Unicode in GCC Rust front-end" and the project will also be mentored by Arthur Cohen and Philip Herron. - Rishi Raj will be workin on a project to "Bypass assembler when generating LTO object files" in that effort will be mentored by Jan Hubička and myself. I'd like to congratulate all of them for putting together really solid proposals and wish them best of luck with their projects. The GSoC program has now entered its "community bonding period" which lasts until May 28th. During this time, contributors should get in touch with their mentors unless you have already done so and probably start looking quite a bit more at GCC in general. In the initial discussion with your mentors, please take a while to talk about the time-frame of your project. If you are happy with the standard 12 week duration (mid-term evaluation deadline on July 14th, final deadline on August 28th) you do not need to do anything. The program can however also accommodate non-standard schedules, see the options at: https://developers.google.com/open-source/gsoc/help/project-dates If you want to change the duration of your project, first please reach an agreement with your mentor and then email me and/or other GSoC Org-admins. The change can be done at any point in the program but note that it will not affect any evaluation which has already started. (In the case of the standard schedule this means that an Org-admin has to enter the change before July 10 to affect the mid-term evaluation and before August 21st to affect the final evaluation). Because GCC targets many computer platforms, you may also find it very useful to get an account on the compile farm so that you can test your code on a variety of architectures. For more details, see https://gcc.gnu.org/wiki/CompileFarm I'd also like to ask all six accepted contributors to take a few minutes to familiarize themselves with the legal pre-requisites that we have for contributing. There are two options. The much simpler one is that copyright remains with you but you provide a "Developer Certificate of Origin" for your contributions. You can do that by adding a "Signed-off-by:" tag to all your patches. The second option is to assign your copyright to the Free Software Foundation (if anyone wants to do this, please let me know and I will help). More information about both is at: https://gcc.gnu.org/contribute.html#legal Last but not least, feel free to raise any question you may have on an appropriate mailing list (https://gcc.gnu.org/lists.html) or say hi to us on the gcc development IRC channel (https://gcc.gnu.org/wiki/GCConIRC). If you have any concerns or questions regarding the organizational part of GSoC 2023 or just don't know who else to reach out to, feel free to contact me throughout the duration of the program. Once more, congratulations and good luck! Martin
Re: GSoC 2023
Hello, we are delighted you found contributing to GCC interesting. On Mon, Mar 27 2023, Igor Putovny via Gcc wrote: > Dear all, > > I am a student of computer science and I was thinking about applying for > Google Summer of Code 2023. Naturally, I wanted to reach out to you before > applying for GCC projects. Please look again at the "Before you apply" section of the idea page https://gcc.gnu.org/wiki/SummerOfCode#Before_you_apply and make sure you are able to build, install and test GCC and then have it generate dumps and step through some function during compilation. > > From selected topics you are interested in, several grabbed my attention: > 1. Bypass assembler when generating LTO object file See https://gcc.gnu.org/pipermail/gcc/2023-March/240833.html > 2. Extend the static analysis pass This is an area, rather than a specific project. I'd suggest you look trough recent archives of the gcc mailing list too, as many projects in that area have been discussed there recently. > 3. Rust Front-End: HIR Dump > 4. Rust Front-End: Improving user errors Please note that Rust-GCC projects are a bit special in the sense that they are often discussed primarily on Zulip of the gcc-rust team: https://gcc-rust.zulipchat.com/ So you may want to reach out to them there as well. > > I have to admit that I feel a bit intimidated by projects of "hard > difficulty", because I have seen how hard it is to find your way in a large > codebase (which GCC definitely is). I definitely agree that GCC source can be hard to go through, especially for newcomers but often even for seasoned contributors when they look at a part they are not familiar with. But when you manage to manage to overcome the difficulty, the project can be very rewarding. And so not hesitate to ask us any specific question you may have here on the mailing list or on IRC. > > Therefore, I would like to ask you for your opinion about these topics and > the level of theoretical/practical experience with compilers you are > expecting. The topics were selected because they are good in various ways and the necessary level of experience is also broadly described on our wiki page. You need to be good at C/C++ and have to be willing (and able) to navigate the big-code base. Figuring it out is work, but doable. > > As for the languages used, I have advanced knowledge of C and intermediate > knowledge of C++. That should be good enough. I think. But you need to do some research of the code related to the topics yourself and you should fairly quickly realize whether your C/C++ skills are sufficient. Good luck! Martin
[GSoC 2023] Rust front-end: HIR dump
Hello, I am writing to express my interest in the HIR dump project in GCC this year. My name is Jiakun Fan, and I am a 3rd year undergraduate student majoring in Computer Science. I believe that this project presents an excellent opportunity for me to make a contribution to the GCC community. I have already done some work about the HIR dump and had discussions with GCCRust developers, which has given me the confidence to tackle this project successfully. If you have any concerns or feedback regarding my proposal, please do not hesitate to contact me. You can find the link to my proposal here: https://hackmd.io/UM6GOcOCRHSl8Ph2rocdVQ?view Best regards, Jiakun Fan
GSoC 2023
Dear all, I am an undergraduate student of computer science and I am interested in GCC projects for Google Summer of Code 2023. >From selected topics you are interested in, several grabbed my attention: 1. Bypass assembler when generating LTO object file 2. Rust Front-End: HIR Dump 3. Rust Front-End: Improving user errors May I ask you for more information about these projects and other knowledge or skills you are expecting? Thank you very much for your time. Best regards, Igor Putovný
GSoC 2023
Dear all, I am a student of computer science and I was thinking about applying for Google Summer of Code 2023. Naturally, I wanted to reach out to you before applying for GCC projects. >From selected topics you are interested in, several grabbed my attention: 1. Bypass assembler when generating LTO object file 2. Extend the static analysis pass 3. Rust Front-End: HIR Dump 4. Rust Front-End: Improving user errors I have to admit that I feel a bit intimidated by projects of "hard difficulty", because I have seen how hard it is to find your way in a large codebase (which GCC definitely is). Therefore, I would like to ask you for your opinion about these topics and the level of theoretical/practical experience with compilers you are expecting. As for the languages used, I have advanced knowledge of C and intermediate knowledge of C++. Thank you very much for your time. Best regards, Igor Putovný
Re: [GSoC 2023] Rust front-end: Improving User Errors
Hello, We are delighted you found contributing to GCC interesting. On Mon, Mar 20 2023, Panagiotis Foliadis via Gcc wrote: > Greetings, > > My name is Panagiotis Foliadis, Ι'm 26 years old and I am from Athens, Greece. > > I'm interesting in the Rust frοnt-end project and especially at Improving > user errors. I'm a self taught > software developer with solid knowledge about Rust, and also Ι'm doing my > internship that mainly uses C. I'm really > interested in the low level side of programming and especially compilers. I > have already built gcc from source and > did some studying on the documentation to acquire some basic knowledge about > the compiler. Please note that Rust-GCC projects are a bit special in the sense that they are often discussed primarily on Zulip of the gcc-rust team: https://gcc-rust.zulipchat.com/ So you may want to reach out to them there as well. > > I'd like some guidance from the mentors prior to making a proposal, if there > is any to give. I assume you have already read through https://gcc.gnu.org/wiki/SummerOfCode The page has guidelines on what we expect to find a proposal. Basically you need to figure out what the project would entail and write it down, with a little bit of detail and milestones. Feel free to ask about any specifics either here on the mailing list or on the Zulip linked above. Good luck! Martin
Re: GSoC 2023
Hello, On Sun, Mar 19 2023, ANKESH PANDEY . wrote: > Hello, > > I am Ankesh Pandey, a 3rd year Computer Science Undergraduate. > > I am interested in contributing for the following projects: We are delighted you found contributing to GCC interesting. > >1. > >Unicode support: Our Lexer and AST do not support Unicode strings and >identifiers, which we need to be a Rust compiler. The project will require >a student to work mostly in the Lexer and AST but the changes here will >ripple all the way through our HIR and code-generation passes. For example, >in implementing Unicode support, it will make sense to ensure we improve >location info, so instead of simply passing around Unicode strings in the >IR's we should create a unique string data structure which also contains >location info to improve our error diagnostics and debug > information. *Difficulty: >Hard Size: 350 hours (large) Mentors: Arthur and/or Philip* >2. > >Improving user errors: We recently merged code enabling the Rust >frontend to emit error codes similarly to rustc. We'd like for gccrs to be >able to emit the same errors codes as rustc, in order to help bridge the >gap between our two testsuites and enable us to eventually run the rustc >one. The student will have to research rustc error codes, their various >guarantees, and emit them throughout the frontend code. We would also like >the code responsible for emitting errors to get more fleshed out and allow >more functionality. Finally, this will also be a good project to start >looking at a better user experience for gccrs: emitting more errors, in >more places, with more hints to the users about ways to fix the > code. *Difficulty: >Medium Size: 175 (medium) Mentors: Arthur and/or Philip* > Please note that Rust-GCC projects are a bit special in the sense that they are often discussed primarily on Zulip of the gcc-rust team: https://gcc-rust.zulipchat.com/ So you may want to reach out to them there as well. > I am really good at C, C++ and have decent experience working with FLEX and > YACC and hence would be an appropriate candidate for the same. > > It would be great if you can give me insights on how I can formalize my > proposal for GSoC 2023. I assume you have already read through https://gcc.gnu.org/wiki/SummerOfCode The page has guidelines on what we expect to find a proposal. Feel free to ask about any specifics either here on the mailing list or on the Zulip linked above. Good luck! Martin
Re: GSoC'2023: Bypass assembler when generating LTO object files: GCC
Hello, please make sure you CC the mailing list in these communications. On Thu, Mar 16 2023, Madhu patel wrote: > Hi, > >>That is an impressive list. On a more specific note, do you have any - >> rudimentary is fine - background in the theory of compilers? Are you >> familiar with concepts like intermediate representation (intermediate >> language)? > > Yes! I have Built the GCC from source and Yes, I do have good knowledge of > compilers. We had this subject in the college curriculum where we studied > intermediate representation. I have good knowledge of C++, c, Java, and > Bash. etc. > >>Great. What are the issues you have encountered? I assume you have >>seen David's guide for newcomers too? If not, have a look at it at >>https://gcc-newbies-guide.readthedocs.io/en/latest/index.html > > Yes, I have built the GCC from scratch on my Linux Machine. > I have written the documentation for the same. And working on understanding > the details of offLoading. > https://www.dropbox.com/scl/fi/ffx7c29f0yfhvbiuvndku/GCC.paper?dl=0=76x89xkzz3h41uemor9ksw6sl Just a note, using images to capture terminal (instead of the text that is there) is a very bad practice. (The configure step is also quite conspicuously missing in your text, why?) > And gone through the > https://gcc-newbies-guide.readthedocs.io/en/latest/index.html > <https://gcc-newbies-guide.readthedocs.io/en/latest/index.html> and did a > basic setup for GCC on my Linux machine. > > Can we schedule a meeting to discuss the project's timeline and specific > tasks that I can take on? > Please let me know your availability. Sorry but no, I am not able to and do not intend to schedule calls with GSoC applicants. I'll be happy to discuss stuff on the mailing-list. Estimating a timeline and coming up with (at least some) milestones of the project is part of the exercise of writing a proposal. GSoC contributors need to demonstrate a certain level of independent thought and initiative - though of course the community is always there to help with specific questions and difficulties. The project has been discussed already in https://gcc.gnu.org/pipermail/gcc/2023-March/240833.html and this message should be enough to get you started. Good luck, Martin > > > On Tue, Mar 14, 2023 at 10:48 PM Martin Jambor wrote: > >> Hello, >> >> We are delighted you found looking into GCC interesting. >> >> On Thu, Mar 09 2023, Madhu patel via Gcc wrote: >> > Hi Jan, >> > >> > I'm interested in working on the project `Bypass assembler when >> generating >> > LTO object files` in the GCC organization through GSoC'2023. >> >> Great, please note that the task as already been discussed on the >> mailing list and some information is available in the archives at >> >>https://gcc.gnu.org/pipermail/gcc/2023-March/240833.html >> >> > >> > I am Madhu Patel, a fourth-year B.Tech. student in Computer Science at >> > IGDTUW, with a CGPA of 8.7/10. I have previously interned at Adobe India, >> > Rabvik Innovations, and FM solutions, and I am currently a research >> intern >> > at IIT Roorkee. I am also working on a research paper on Linux Kernel >> > Evolution for the USENIX publication. Moreover, my research paper on >> Stock >> > Price Prediction was recently accepted at the IEEE Conference. You can >> find >> > more information about my work on my LinkedIn and GitHub profiles. >> >> That is an impressive list. On a more specific note, do you have any - >> rudimentary is fine - background in the theory of compilers? Are you >> familiar with concepts like intermediate representation (intermediate >> language)? >> >> > >> > Please suggest a few initial tasks I can work on during the application >> > period and attach them to my application. I have already prepared a >> > timeline/planner, great if you could have a look at it and suggest any >> > enhancements. Additionally, I have signed in to the mailing lists, and >> IRCs >> > and done the initial tasks as described on the project page [1] >> > <https://gcc.gnu.org/wiki/SummerOfCode>. >> >> Great. What are the issues you have encountered? I assume you have >> seen David's guide for newcomers too? If not, have a look at it at >> https://gcc-newbies-guide.readthedocs.io/en/latest/index.html >> >> I am afraid there are not very many small issues or problems that can be >> dealt with in a few weeks. Instead, I would encourage you to keep >> investigating the code, particularly around the areas described in the >> mailing list post I linked above, and start thinking about how you'd >> achieve the overall goal. Feel free to ask any specific questions you >> might have about the project and GCC development in general here. >> >> Good luck! >> >> Martin >> >>
GSOC 2023 Proposal about MetaData Exports by Parthib Datta
There is my GSOC 2023 Proposal about the Metadata Exports project please review it and let me know what you guys think about it?? GSOC Proposal for Metadata Exports in Rust-GCC by Parthib Datta.docx Description: MS-Word 2007 document
[GSoC 2023] Rust front-end: Improving User Errors
Greetings, My name is Panagiotis Foliadis, Ι'm 26 years old and I am from Athens, Greece. I'm interesting in the Rust frοnt-end project and especially at Improving user errors. I'm a self taught software developer with solid knowledge about Rust, and also Ι'm doing my internship that mainly uses C. I'm really interested in the low level side of programming and especially compilers. I have already built gcc from source and did some studying on the documentation to acquire some basic knowledge about the compiler. I'd like some guidance from the mentors prior to making a proposal, if there is any to give.
GSoC 2023
Hello, I am Ankesh Pandey, a 3rd year Computer Science Undergraduate. I am interested in contributing for the following projects: 1. Unicode support: Our Lexer and AST do not support Unicode strings and identifiers, which we need to be a Rust compiler. The project will require a student to work mostly in the Lexer and AST but the changes here will ripple all the way through our HIR and code-generation passes. For example, in implementing Unicode support, it will make sense to ensure we improve location info, so instead of simply passing around Unicode strings in the IR's we should create a unique string data structure which also contains location info to improve our error diagnostics and debug information. *Difficulty: Hard Size: 350 hours (large) Mentors: Arthur and/or Philip* 2. Improving user errors: We recently merged code enabling the Rust frontend to emit error codes similarly to rustc. We'd like for gccrs to be able to emit the same errors codes as rustc, in order to help bridge the gap between our two testsuites and enable us to eventually run the rustc one. The student will have to research rustc error codes, their various guarantees, and emit them throughout the frontend code. We would also like the code responsible for emitting errors to get more fleshed out and allow more functionality. Finally, this will also be a good project to start looking at a better user experience for gccrs: emitting more errors, in more places, with more hints to the users about ways to fix the code. *Difficulty: Medium Size: 175 (medium) Mentors: Arthur and/or Philip* I am really good at C, C++ and have decent experience working with FLEX and YACC and hence would be an appropriate candidate for the same. It would be great if you can give me insights on how I can formalize my proposal for GSoC 2023. Hoping to contribute to the organization through GSoC 2023. Thank you. -- The information contained in this electronic communication is intended solely for the individual(s) or entity to which it is addressed. It may contain proprietary, confidential and/or legally privileged information. Any review, retransmission, dissemination, printing, copying or other use of, or taking any action in reliance on the contents of this information by person(s) or entities other than the intended recipient is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us by responding to this email or telephone and immediately and permanently delete all copies of this message and any attachments from your system(s). The contents of this message do not necessarily represent the views or policies of BITS Pilani.
Re: GSoC'2023: Separate Host Process Offloading: GCC
Hi Thomas > (As you've sent your equally worded > "GSoC'2023: Bypass assembler when generating LTO object files: GCC" email > to , let me also Cc my reply here to that list, so that > others may contribute, too.) Thank you for looping folks in; I'm equally interested in both projects, and it would be great if you can suggest a few tasks that I can take up. >>Building GCC and producing test results would be one obvious first task, > have you worked on that already? > <https://gcc.gnu.org/wiki/#Getting_Started_with_GCC_Development> has some > pointers to get started. If you have specific questions, we're happy to > help, of course. Yes, I have built the GCC from scratch on my Linux Machine. I have written the documentation for the same. And working on understanding the details of offLoading. https://www.dropbox.com/scl/fi/ffx7c29f0yfhvbiuvndku/GCC.paper?dl=0=76x89xkzz3h41uemor9ksw6sl > Which specifically? I've subscribed to this mailing list. gcc@gcc.gnu.org Can we schedule a meeting to discuss the project's timeline and specific tasks that I can take on? Please let me know your availability, as my time zone is IST. I have developed an understanding of offloading. ~Madhu
Re: GSoC'2023: Bypass assembler when generating LTO object files: GCC
Hello, We are delighted you found looking into GCC interesting. On Thu, Mar 09 2023, Madhu patel via Gcc wrote: > Hi Jan, > > I'm interested in working on the project `Bypass assembler when generating > LTO object files` in the GCC organization through GSoC'2023. Great, please note that the task as already been discussed on the mailing list and some information is available in the archives at https://gcc.gnu.org/pipermail/gcc/2023-March/240833.html > > I am Madhu Patel, a fourth-year B.Tech. student in Computer Science at > IGDTUW, with a CGPA of 8.7/10. I have previously interned at Adobe India, > Rabvik Innovations, and FM solutions, and I am currently a research intern > at IIT Roorkee. I am also working on a research paper on Linux Kernel > Evolution for the USENIX publication. Moreover, my research paper on Stock > Price Prediction was recently accepted at the IEEE Conference. You can find > more information about my work on my LinkedIn and GitHub profiles. That is an impressive list. On a more specific note, do you have any - rudimentary is fine - background in the theory of compilers? Are you familiar with concepts like intermediate representation (intermediate language)? > > Please suggest a few initial tasks I can work on during the application > period and attach them to my application. I have already prepared a > timeline/planner, great if you could have a look at it and suggest any > enhancements. Additionally, I have signed in to the mailing lists, and IRCs > and done the initial tasks as described on the project page [1] > <https://gcc.gnu.org/wiki/SummerOfCode>. Great. What are the issues you have encountered? I assume you have seen David's guide for newcomers too? If not, have a look at it at https://gcc-newbies-guide.readthedocs.io/en/latest/index.html I am afraid there are not very many small issues or problems that can be dealt with in a few weeks. Instead, I would encourage you to keep investigating the code, particularly around the areas described in the mailing list post I linked above, and start thinking about how you'd achieve the overall goal. Feel free to ask any specific questions you might have about the project and GCC development in general here. Good luck! Martin
Re: GSoC'2023: Separate Host Process Offloading: GCC
Hi! Sorry, let me try again -- our IT department likes to garble emails in order to attach a "disclaimer"... On 2023-03-13T21:37:24+0100, I wrote: > Hi Madhu! > > (As you've sent your equally worded > "GSoC'2023: Bypass assembler when generating LTO object files: GCC" email > to , let me also Cc my reply here to that list, so that > others may contribute, too.) > > > On 2023-03-09T01:36:02+0530, Madhu patel wrote: >> I'm interested in working on the project `Separate Host Process Offloading` >> in the GCC organization through GSoC'2023. > > Great, and welcome to GCC! :-) > >> Please suggest a few initial tasks I can work on during the application >> period and attach them to my application. > > Building GCC and producing test results would be one obvious first task, > have you worked on that already? > <https://gcc.gnu.org/wiki/#Getting_Started_with_GCC_Development> has some > pointers to get started. If you have specific questions, we're happy to > help, of course. > > Then, get familiar with the basic concepts of code offloading in GCC. > <https://gcc.gnu.org/wiki/Offloading> is the best (only?) we have, > unfortunately, and it's somewhat out of date, so beware, sorry. Looking > at existing libgomp plugins may help: 'libgomp/plugin/plugin-*.c', and > actually also the very simple 'libgomp/oacc-host.c'. That's essentially > the API you need to care about (for OpenACC; but OpenMP 'target' also > won't require much more, for a start). > > Make some thoughts (or actual experiments) about how we could > use/implement a separate host process for code offloading. > >> I have already prepared a >> timeline/planner, great if you could have a look at it and suggest any >> enhancements. > > That wasn't attached to or referred to in your email? > >> Additionally, I have signed in to the mailing lists, and IRCs >> and done the initial tasks as described on the project page [1] >> <https://gcc.gnu.org/wiki/SummerOfCode>. > > Which specifically? Grüße Thomas - Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
Re: GSoC'2023: Separate Host Process Offloading: GCC
- Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955 --- Begin Message --- Hi Madhu! (As you've sent your equally worded "GSoC'2023: Bypass assembler when generating LTO object files: GCC" email to , let me also Cc my reply here to that list, so that others may contribute, too.) On 2023-03-09T01:36:02+0530, Madhu patel wrote: > I'm interested in working on the project `Separate Host Process Offloading` > in the GCC organization through GSoC'2023. Great, and welcome to GCC! :-) > Please suggest a few initial tasks I can work on during the application > period and attach them to my application. Building GCC and producing test results would be one obvious first task, have you worked on that already? <https://gcc.gnu.org/wiki/#Getting_Started_with_GCC_Development> has some pointers to get started. If you have specific questions, we're happy to help, of course. Then, get familiar with the basic concepts of code offloading in GCC. <https://gcc.gnu.org/wiki/Offloading> is the best (only?) we have, unfortunately, and it's somewhat out of date, so beware, sorry. Looking at existing libgomp plugins may help: 'libgomp/plugin/plugin-*.c', and actually also the very simple 'libgomp/oacc-host.c'. That's essentially the API you need to care about (for OpenACC; but OpenMP 'target' also won't require much more, for a start). Make some thoughts (or actual experiments) about how we could use/implement a separate host process for code offloading. > I have already prepared a > timeline/planner, great if you could have a look at it and suggest any > enhancements. That wasn't attached to or referred to in your email? > Additionally, I have signed in to the mailing lists, and IRCs > and done the initial tasks as described on the project page [1] > <https://gcc.gnu.org/wiki/SummerOfCode>. Which specifically? Grüße Thomas signature.asc Description: PGP signature --- End Message ---
GSoC'2023: Bypass assembler when generating LTO object files: GCC
Hi Jan, I'm interested in working on the project `Bypass assembler when generating LTO object files` in the GCC organization through GSoC'2023. I am Madhu Patel, a fourth-year B.Tech. student in Computer Science at IGDTUW, with a CGPA of 8.7/10. I have previously interned at Adobe India, Rabvik Innovations, and FM solutions, and I am currently a research intern at IIT Roorkee. I am also working on a research paper on Linux Kernel Evolution for the USENIX publication. Moreover, my research paper on Stock Price Prediction was recently accepted at the IEEE Conference. You can find more information about my work on my LinkedIn and GitHub profiles. Please suggest a few initial tasks I can work on during the application period and attach them to my application. I have already prepared a timeline/planner, great if you could have a look at it and suggest any enhancements. Additionally, I have signed in to the mailing lists, and IRCs and done the initial tasks as described on the project page [1] <https://gcc.gnu.org/wiki/SummerOfCode>. Thanks, Madhu Patel LinkedIn <https://www.linkedin.com/in/madhu-patel/> | Github <https://github.com/Madhupatel08>
Re: GSOC 2023 Contribution Request
Hi Kritika, On Wed, Feb 22, 2023 at 6:49 AM Kritika Rag via Gcc 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. >
Re: GSOC 2023 Contribution Request
Thank you for your response Martin. Actually I sent this mail a week ago and yeah now the wiki page of gcc has been updated (although I'm very much sure these topics were listed over there but that's totally fine) and so today itself I sent another mail with expressing an interest in working on "C++ : Implement compiler built-in traits for the standard library traits" project. And I've been following Anshul's advice and have been exploring the gcc codebase. Further, I hope to get guidance on my newly selected project interest. Thank you so much again. On Wed, 22 Feb, 2023, 21:46 Martin Jambor, wrote: > Hello Kritika, > > we are delighted that you decided to apply for GSoC and that you are > interested in choosing GCC as the project to contribute to. > > On Mon, Feb 13 2023, Kritika Rag via Gcc wrote: > > Hello Sir/Mam, > > > > 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. After going through all the projects listed on GCC Wiki > > <https://gcc.gnu.org/wiki/SummerOfCode#Other_Project_Ideas>, these are > the > > projects(any one of them) to which I would like to contribute: > > > >1. Bug Patrol and primarily Analyze Failing Test Cases – Whether I'm > >practicing algorithms on Leetcode, GFG, etc., or giving CP contests on > >CodeChef, Codeforces, etc., Test case failures are something I > encounter > >daily. Working on the project would be an interesting dig for me to > learn > >about the inner workings of something that I see daily and make > >improvements to it. > >2. Library Infrastructure - As quoted *"These tasks are about > improving > >the utility routine library used by GCC. If you like data structures, > these > >may be for you", *and being a data structures enthusiast I do believe > >that I'll be able to put my best knowledge to use in this project. > > I am somewhat confused here, I do not think either of the two project > ideas is listed even in the rather messy "other projects" section of our > GSoC page. Even the quotes do not seem to be quotes, the word "utility" > does not appear on that page anywhere. > > What is worse, I don't understand what the second project would be and I > don't think the first one would be appropriate as it is impossible to > set goals about unknown bugs that might arrive in the future. Looking > at the already failing testcases in our testcase do not constitute a > reasonable project either. There are not that many and those that exist > are there for a reason that is difficult to overcome. > > So I am afraid that you'll need to look again. find an actual area of > the project that interests you most and look for a project with > milestones. The projects that are actually listed at > https://gcc.gnu.org/wiki/SummerOfCode might be a good start. > > Ankur has provided you with excellent summary of steps to get more > familiar with GCC code base, definitely heed his advice too. > > Good luck! > > Martin >
Re: GSOC 2023 Contribution Request
Hello Kritika, we are delighted that you decided to apply for GSoC and that you are interested in choosing GCC as the project to contribute to. On Mon, Feb 13 2023, Kritika Rag via Gcc wrote: > Hello Sir/Mam, > > 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. After going through all the projects listed on GCC Wiki > <https://gcc.gnu.org/wiki/SummerOfCode#Other_Project_Ideas>, these are the > projects(any one of them) to which I would like to contribute: > >1. Bug Patrol and primarily Analyze Failing Test Cases – Whether I'm >practicing algorithms on Leetcode, GFG, etc., or giving CP contests on >CodeChef, Codeforces, etc., Test case failures are something I encounter >daily. Working on the project would be an interesting dig for me to learn >about the inner workings of something that I see daily and make >improvements to it. >2. Library Infrastructure - As quoted *"These tasks are about improving >the utility routine library used by GCC. If you like data structures, these >may be for you", *and being a data structures enthusiast I do believe >that I'll be able to put my best knowledge to use in this project. I am somewhat confused here, I do not think either of the two project ideas is listed even in the rather messy "other projects" section of our GSoC page. Even the quotes do not seem to be quotes, the word "utility" does not appear on that page anywhere. What is worse, I don't understand what the second project would be and I don't think the first one would be appropriate as it is impossible to set goals about unknown bugs that might arrive in the future. Looking at the already failing testcases in our testcase do not constitute a reasonable project either. There are not that many and those that exist are there for a reason that is difficult to overcome. So I am afraid that you'll need to look again. find an actual area of the project that interests you most and look for a project with milestones. The projects that are actually listed at https://gcc.gnu.org/wiki/SummerOfCode might be a good start. Ankur has provided you with excellent summary of steps to get more familiar with GCC code base, definitely heed his advice too. Good luck! Martin
GSOC 2023 Contribution Request
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. 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. Thank you so much and I hope to hear from you soon.
Re: GSOC 2023 Contribution Request
Hi, I am neither the org-admin for GSoC, nor a mentor for any of the proposed projects. Just a community member like you. Here are a few things you can do till the time you get a response from either of those: - Try building gcc from source if you haven't till now, refer the docs https://gcc.gnu.org/install/ for detailed information and try building with bootstrap disabled if you want to save some time. Also it is recommended to build a debuggable version ( see next point for details ) so that you can efficiently use a debugger to step through the source code. - Once you have a proper version built from source, you can now use a debugger ( preferably gdb ) on it to get better understanding of the control flow. You can read the official docs ( https://gcc.gnu.org/wiki/DebuggingGCC#gccbuilddebug ) or the gcc-newbies-guide by David Malcolm ( https://gcc-newbies-guide.readthedocs.io/en/latest/debugging.html ) for more information and instructions about debugging gcc. - Speaking of gcc-newbies-guide by David Malcolm, it is actually an amazing source to get started for new-comers ( https://gcc-newbies-guide.readthedocs.io/en/latest/index.html ) Although Google is yet to announce list of selected organizations. Most of the stuff I mentioned is already present in the "Before you apply" ( https://gcc.gnu.org/wiki/SummerOfCode#Before_you_apply ) section of gcc's summer of code page. - Ankur > On 13-Feb-2023, at 7:04 PM, Kritika Rag via Gcc wrote: > > Hello Sir/Mam, > > > > 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. After going through all the projects listed on GCC Wiki > <https://gcc.gnu.org/wiki/SummerOfCode#Other_Project_Ideas>, these are the > projects(any one of them) to which I would like to contribute: > > 1. Bug Patrol and primarily Analyze Failing Test Cases – Whether I'm > practicing algorithms on Leetcode, GFG, etc., or giving CP contests on > CodeChef, Codeforces, etc., Test case failures are something I encounter > daily. Working on the project would be an interesting dig for me to learn > about the inner workings of something that I see daily and make > improvements to it. > 2. Library Infrastructure - As quoted *"These tasks are about improving > the utility routine library used by GCC. If you like data structures, these > may be for you", *and being a data structures enthusiast I do believe > that I'll be able to put my best knowledge to use in this project. > > Lastly, thank you so much for providing these opportunities, I would be > grateful if you would provide me the opportunity to work with your > organization. Looking forward to hearing from you soon. > > Thanks and Regards, > Kritika Rag > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
Re: GSOC 2023 Contribution Request
Hello Team, Just want to know is there any update on my application? On Mon, 13 Feb, 2023, 19:04 Kritika Rag, wrote: > Hello Sir/Mam, > > > > 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. After going through all the projects listed on GCC Wiki > <https://gcc.gnu.org/wiki/SummerOfCode#Other_Project_Ideas>, these are > the projects(any one of them) to which I would like to contribute: > >1. Bug Patrol and primarily Analyze Failing Test Cases – Whether I'm >practicing algorithms on Leetcode, GFG, etc., or giving CP contests on >CodeChef, Codeforces, etc., Test case failures are something I encounter >daily. Working on the project would be an interesting dig for me to learn >about the inner workings of something that I see daily and make >improvements to it. >2. Library Infrastructure - As quoted *"These tasks are about >improving the utility routine library used by GCC. If you like data >structures, these may be for you", *and being a data structures >enthusiast I do believe that I'll be able to put my best knowledge to use >in this project. > > Lastly, thank you so much for providing these opportunities, I would be > grateful if you would provide me the opportunity to work with your > organization. Looking forward to hearing from you soon. > > Thanks and Regards, > Kritika Rag > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows > > >
GSOC 2023 Contribution Request
Hello Sir/Mam, 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. After going through all the projects listed on GCC Wiki <https://gcc.gnu.org/wiki/SummerOfCode#Other_Project_Ideas>, these are the projects(any one of them) to which I would like to contribute: 1. Bug Patrol and primarily Analyze Failing Test Cases – Whether I'm practicing algorithms on Leetcode, GFG, etc., or giving CP contests on CodeChef, Codeforces, etc., Test case failures are something I encounter daily. Working on the project would be an interesting dig for me to learn about the inner workings of something that I see daily and make improvements to it. 2. Library Infrastructure - As quoted *"These tasks are about improving the utility routine library used by GCC. If you like data structures, these may be for you", *and being a data structures enthusiast I do believe that I'll be able to put my best knowledge to use in this project. Lastly, thank you so much for providing these opportunities, I would be grateful if you would provide me the opportunity to work with your organization. Looking forward to hearing from you soon. Thanks and Regards, Kritika Rag Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
GCC GSoC 2023: Call for project ideas and mentors
Hello, another year has passed and Google has announced there will be again Google Summer of Code (GsoC) in 2023 and the deadline for organizations to apply is already approaching (February 7th). I'd like to volunteer to be the main Org Admin for GCC again so let me know if you think I shouldn't or that someone else should or if you want to do it instead, but otherwise I'll assume that I will. The most important bit: I would like to ask all (moderately) seasoned GCC contributors to consider mentoring a student this year and ideally also come up with a project that they would like to lead. I'm collecting proposal on our wiki page https://gcc.gnu.org/wiki/SummerOfCode - feel free to add yours to the top list there. Or, if you are unsure, post your offer and project idea as a reply here to the mailing list. = At this point, we need to collect list of project ideas. Eventually, each listed project idea should have: a) a project title, b) more detailed description of the project (2-5 sentences), c) expected outcomes (we do have a catch-almost-all formulation that outcome is generally patches at the bottom of the list in the wiki), d) skills required/preferred, e) project size (whether approximately 175 or 350 hours), f) difficulty (easy, hard or medium, but we don't really have easy projects), and g) expected mentors. Project ideas that come without an offer to also mentor them are always fun to discuss, by all means feel free to reply to this email with yours and I will attempt to find a mentor, but please be aware that we can only use the suggestion it if we actually find one or ideally two. Everybody in the GCC community is invited to go over https://gcc.gnu.org/wiki/SummerOfCode and remove any outdated or otherwise bad project suggestions and help improve viable ones. Finally, please continue helping (prospective) students figure stuff out about GCC like you have always done in the past. As far as I know, GSoC 2023 should be quite similar to the last year, the most important parameters probably are these: - Contributors (formerly students) must either be students or be "beginners to open source" (or both). - There are two project sizes, roughly 175 hours (medium-sized) and roughly 350 hours (large) in total. - Timing should be pretty much as flexible as last year. Two years ago it was 12 weeks for everyone but now projects can take anywhere between 10 and 22 weeks. (But I'd prefer if we tried to fit into 20 at maximum, even that means deadlines would get close to stage 1 end.) There will be one mid-term and one final evaluation. For further details you can see: - The announcement of GSoC 2023: https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html - GSoC rules: https://summerofcode.withgoogle.com/rules - The detailed GSoC 2023 timeline: https://developers.google.com/open-source/gsoc/timeline - Elaborate project idea guidelines: https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list Thank you for your participation and help. Let's hope we attract some great contributors again this year. Martin
GCC GSoC 2023: Call for project ideas and mentors
Hello, another year has passed and Google has announced there will be again Google Summer of Code (GsoC) in 2023 and the deadline for organizations to apply is already approaching (February 7th). I'd like to volunteer to be the main Org Admin for GCC again so let me know if you think I shouldn't or that someone else should or if you want to do it instead, but otherwise I'll assume that I will. The most important bit: I would like to ask all (moderately) seasoned GCC contributors to consider mentoring a student this year and ideally also come up with a project that they would like to lead. I'm collecting proposal on our wiki page https://gcc.gnu.org/wiki/SummerOfCode - feel free to add yours to the top list there. Or, if you are unsure, post your offer and project idea as a reply here to the mailing list. = At this point, we need to collect list of project ideas. Eventually, each listed project idea should have: a) a project title, b) more detailed description of the project (2-5 sentences), c) expected outcomes (we do have a catch-almost-all formulation that outcome is generally patches at the bottom of the list in the wiki), d) skills required/preferred, e) project size (whether approximately 175 or 350 hours), f) difficulty (easy, hard or medium, but we don't really have easy projects), and g) expected mentors. Project ideas that come without an offer to also mentor them are always fun to discuss, by all means feel free to reply to this email with yours and I will attempt to find a mentor, but please be aware that we can only use the suggestion it if we actually find one or ideally two. Everybody in the GCC community is invited to go over https://gcc.gnu.org/wiki/SummerOfCode and remove any outdated or otherwise bad project suggestions and help improve viable ones. Finally, please continue helping (prospective) students figure stuff out about GCC like you have always done in the past. As far as I know, GSoC 2023 should be quite similar to the last year, the most important parameters probably are these: - Contributors (formerly students) must either be students or be "beginners to open source" (or both). - There are two project sizes, roughly 175 hours (medium-sized) and roughly 350 hours (large) in total. - Timing should be pretty much as flexible as last year. Two years ago it was 12 weeks for everyone but now projects can take anywhere between 10 and 22 weeks. (But I'd prefer if we tried to fit into 20 at maximum, even that means deadlines would get close to stage 1 end.) There will be one mid-term and one final evaluation. For further details you can see: - The announcement of GSoC 2023: https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html - GSoC rules: https://summerofcode.withgoogle.com/rules - The detailed GSoC 2023 timeline: https://developers.google.com/open-source/gsoc/timeline - Elaborate project idea guidelines: https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list Thank you for your participation and help. Let's hope we attract some great contributors again this year. Martin -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
