RE: Open Available Projects for Google Summer of Code 2024
On Mon, Jan 22 2024, Vedant Tewari wrote: Hello Vedant, > Hello, > I am expressing my interest as a potential gsoc participant, based on this > https://gcc.gnu.org/wiki/SummerOfCode, are there any available projects > that you might recommend or might be best suited for a potential proposal > for the upcoming gsoc. I am interested in working with optimization passes > and was hoping for some guidance! We are delighted you found contributing to GCC interesting. GCC has applied to be part of GSoC 2024 but of course selected organizations have not been announced yet this year. The idea page is still undergoing review to reflect changes over the last year, nevertheless a lot of the ideas will stay the same or look very similar. It currently does not contain much work on any general optimization pass, the reason is that what still remains to be done is often difficult and not easily explained to a complete newcomer. But we are still looking for items to populate that list and so we still may find some. So keep looking there but I'd also encourage you to come and discuss ideas on our IRC channel. >From what we already have, I'd suggest looking into what is called "Separate Host Process Offloading." While it is not optimization work itself, it would introduce you to the world of offloading and I believe there is still a lot of unexplored optimization opportunities when it comes to passing and using more information from the main host program to the bits running elsewhere. But in order to experiment and test, we need a vehicle to do the offloading simply. Make also sure to go through 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 during compilation. Definitely feel free to ask for help on the mailing list (which I'm CCing) with any specific GCC development issues you may encounter. Good luck! Martin
Re: GSoC: Application for Rust Front-End Project at GCC
Hello Arpit, We are very happy that you found contributing to GCC-rust interesting. GCC has applied to be part of GSoC 2024 but of course selected organizations have not been announced yet this year. On Sat, Dec 30 2023, CS21B062 ARPIT GUPTA wrote: > Dear GCC Community, > > I hope this email finds you well. My name is Arpit and I am writing to > express my interest in participating in GSoC, specifically for the > Rust Front-End project at GCC. Having completed an internship in > Compiler Design at IIT Hyderabad in my IInd Year , where I gained > hands-on experience in code compliance, optimization analysis, and > cross-compilation, I am eager to contribute to the development of the > Rust compiler front-end. 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 I suggest you also reach out to them there as well. You can refer to your email in the archives (https://gcc.gnu.org/pipermail/gcc/2023-December/243089.html) so that you don't have to repeat everything. Good luck! Martin > > After carefully reviewing the available projects, I am particularly > interested in the following project: > > Project Choice: > Rust Front-End, all the subdomains > > Project Description: > Rust supports several metadata outputs crucial for importing crates. > The goal of this project is to extend the support for metadata exports > in the Rust Front-End being developed by GCC. I am confident in my > understanding of compilation and linking processes, which will be > essential for this project. I am excited about the opportunity to work > on this challenging task and contribute to the completion of metadata > exports. > > Why This Project: > I believe that improving metadata exports is a crucial step towards > enhancing the interoperability of the Rust compiler with other tools > and platforms. This effort aligns with my passion for compiler design > and would significantly contribute to the overall functionality of the > Rust Front-End. Moreover, as an intern I have already developed some > compliance checkers using clang for C language in accordance with > AUTOSAR. > > Proposed Timeline: > > Weeks 1-2: In-depth analysis of the existing metadata export framework > in GCC and understanding the requirements for Rust. > Weeks 3-5: Implementation of basic metadata export functionality for > the Rust Front-End. > Weeks 6-8: Testing and debugging of the implemented features, > addressing any issues that may arise during the integration. > Weeks 9-12: Fine-tuning, optimization, and documentation of the > metadata export process, ensuring it meets the project's goals. > > I am committed to engaging with the community throughout the > development process, seeking feedback, and incorporating suggestions > to ensure the success of the project. I have subscribed to the > gcc@gcc.gnu.org mailing list and will actively participate in > discussions regarding the Rust Front-End project. > > I would appreciate any feedback or guidance on my proposed project and > timeline. I am eager to contribute to the GCC community and make a > meaningful impact on the Rust Front-End project. > > Thank you for considering my application. I look forward to the > opportunity to contribute to the GCC community during GSoC 2023. > > Best regards, > Arpit Gupta, > Code Club Head > ph: 8299480636
Re: GSoC 2024 Application: Rupali Paliwal
Hello, We are delighted you found contributing to GCC interesting. GCC has applied to be part of GSoC 2024 but of course selected organizations have not been announced yet this year. More comments inline. On Mon, Jan 22 2024, Rupali P via Gcc wrote: > Respected GSoC Review Team, > > > I am writing to express my enthusiastic interest in participating in Google > Summer of Code 2024 with Tobias Burnus. Below, I've outlined my project > idea, shared insights into my background and passion for open source, and > demonstrated my commitment to contributing to Tobias Burnus. > > > *Project Proposal:* > > *Title*: > > *Fortran – improved argument compile-time checking* – The compiler does > check for the arguments in the *same* file – but it could do better in some > cases, i.e. checking better the interface data or updating the expected > input better from the user. This project would be mentored by Tobias > Burnus. Required skills include C/C++; some knowledge of Fortran helps, but > is not needed. > > > *1. Idea Description:* > > *Project Title: *Fortran – Improved Argument Compile-Time Checking. > > *Idea Description:.* > > The goal of this project is to enhance the compile-time checking > capabilities of the Fortran compiler, specifically focusing on improving > the analysis of arguments within the same file. While the current compiler > performs basic argument checks, there is room for improvement, particularly > in checking interface data and updating expected input information derived > from the usage context. > > > *Key Components:.* > > 1. .Interface Data Analysis:. > > - Implement an advanced analysis mechanism to better check interface data > related to function and subroutine arguments. I am afraid this needs more detail, especially at least roughly how you plan to achieve that. Please read through https://gcc.gnu.org/wiki/SummerOfCode#Application > > - Explore ways to detect and address discrepancies in argument > specifications within the Fortran code. I'm afraid I don't understand what you mean. Anything beyond giving an error or warning? > > 2. .Optimizing Expected Input:. > > - Develop strategies to improve the compiler's ability to update expected > input information based on the usage of arguments in the code. What do you mean by "update input"? > > - Enhance the accuracy of expected input to provide more meaningful > feedback to developers during the compilation process. > This is a way too general statement as well. > > Mentor: > > Tobias Burnus will serve as the mentor for this project, offering guidance > and expertise in compiler development. > > > *2. Enthusiasm and Devotion:* > > Thrilled about the Fortran – Improved Argument Compile-Time Checking > project in GSoC 2024 under Tobias Burnus' mentorship. My passion for > compiler development, Linux OS internals, and open-source fuels my > eagerness to enhance Fortran's compile-time checking, ensuring code > reliability and contributing meaningfully to the community. Enthusiasm is a wonderful thing but you also need to demonstrate competence. 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. Try to identify places in the compiler which would need changing to achieve the project goal. Feel free to ask specific technical questions on this list and IRC as you do so. [...] > > > *4. .Targeted Application:.* > > - Emphasize the importance of tailoring each application to the specific > mentoring organization and project. ??? > > - Mention unique aspects of the project and organization that align with > your skills and interests. > ??? But you don't really need to do either if you can convince us you have not just the determination but also the skills to successfully finish the project. So look at our code, try it out an tell us what you'd change there to accomplish the project goals. Good luck, Martin
[no subject]
An ad request is counted whenever your site requests ads to be displayed. It is the number of ad units that requested ads (for content ads) or search queries (for search ads). We report an ad request each time a request was sent, even if no ads were returned.
