Re: Welcome GCC GSoC 2026 participants!

Hi,

I've decided to go with the FSF copyright assignment option. Could you
please help me with the process and let me know what I need to do next?

Best Regards,
Enes

On Fri, May 1, 2026 at 12:31 AM Martin Jambor <[email protected]> wrote:

> Hello,
>
> I am pleased to announce that we will have five contributors working
> on GCC as part of their Google Summer of Code (GSoC) projects in 2026,
> most of them working on "large" projects!
>
> Before giving the list of accepted project, I'd like to point out that
> the number of very solid proposals was exceptionally high this year
> and it was very difficult to rank the selected projects.  Most of the
> unsuccessful applications were very good too but the sad reality is
> that we had to rank the proposals somehow and received "only" five
> slots.
>
> In no particular order, the selected GCC GSoC 2026 project are:
>
> - Egas Ribeiro will be Extending C++ Support in GCC Static Analyzer
>   and will be mentored by David Malcolm.
>
> - Enes Çevik will join the GCC Rust team in order to Add
>   Infrastructure to Compile the Rust 'alloc' Crate, the project will
>   be mentored by Arthur Cohen and Pierre-Emmanuel Patry.
>
> - Janet Chien will be working on the second GCC Rust project looking
>   to Add infrastructure to handle the "Drop" trait, which will also be
>   mentored by Arthur Cohen and Pierre-Emmanuel Patry.
>
> - Nchang Roy will be implementing Libgomp Optimizations for Scheduler
>   Guided OpenMP Execution in Cloud VMs and will be mentored by Himadri
>   Chhaya-Shailesh, Thomas Schwinge, Andrea Righi and Tobias Burnus.
>
> - Sebastian Galindo will be working on a project to Enhance OpenACC
>   Support in GCC and will be mentored by Thomas Schwinge and Tobias
>   Burnus.
>
> I'd like to congratulate all of them for putting together truly 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 24th.  During this time, contributors should get in
> touch with their mentors unless they 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 10th,
> final deadline on August 24th) you do not need to do anything.  The
> program can however also accommodate other schedules up to 22 weeks
> (the page listing deadlines for each possible duration still probably
> needs to be updated).
>
> 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 as
> long as you are not asking to extend an evaluation which has already
> started.  In the case of the standard schedule this means that an
> Org-admin has to enter the change into the "GSoC dashboard" before
> July 6th to affect the mid-term evaluation and before August 17th to
> affect the final evaluation.  We will not be able to help you once any
> particular evaluation has started.
>
> I'd also like to ask all five 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 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, I'd like to ask all five of you to subscribe to
> the gcc mailing (if you have not done so already) which you can do at
> https://gcc.gnu.org/mailman/listinfo/gcc - a must for any true member
> of the GCC community.  We will also ask you to send brief but regular
> status updates there, more details on that will follow.  Note that you
> do not have to subscribe to the gcc-patches mailing list - although
> you certainly can and (with the exception of the GCC Rust projects)
> you should briefly look at its archives to see how and in what format
> you'll be expected to submit patches for review.
>
> Because GCC targets many computer platforms, when the time comes to
> test your patches 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
>
> 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 2026 or just don't know who else to reach out to, feel
> free to contact me and/or other GCC GSoC Org-admins throughout the
> duration of the program.
>
> Once more, congratulations and good luck!
>
> Martin
>
>