Re: "GSoC"

[Martin Jambor <mjambor@suse.cz>]

Hello,

I actually forgot to CC the mailing list as I promised to, so
re-sending.

Sorry,

Martin


On Sat, Mar 30 2024, Martin Jambor wrote:
> Hello,
>
> and sorry for replying late, I have faced a few urgent interruptions
> last week and unfortunately it is also a short week because of Easter -
> and so will be the upcoming one, I'm afraid, as Monday is also public
> holiday in many countries.
>
> Some comments are inline below.
>
> On Wed, Mar 27 2024, M Hamza Nadeem wrote:
>> Hi Martin,
>>
>> *Firstly* ,I have diligently followed the instructions provided in the
>> "Before you apply" section of the GCC GSoC page and successfully completed
>> the tasks outlined therein. I have built, installed, and tested GCC . I
>> have attached the screenshot of it below .
>> [image: gmail.png]
>>
>>  *Secondly*, I had Generated dumps of the Intermediate Representation of a
>> simple compiled program and stepped through some functions during
>> compilation using a debugger. I am studying  more deeply this concept at
>> https://www.geeksforgeeks.org/intermediate-code-generation-in-compiler-design/
>>  .
>>
>
> Thank you, that is important.
>
>> *Thirdly *, After conducting a thorough review of the available projects
>> listed on the GCC GSoC page, I have identified a project that aligns
>> closely with my interests and skill set. The project titled "Improve
>> nothrow Detection in GCC," under the mentorship of Jan Hubička,
>> particularly caught my attention.
>>
>> The prospect of extending the GCC middle-end to comprehend the semantics of
>> a __cxa_throw call and enable type-sensitive propagation of thrown
>> exceptions  I am particularly drawn to this project due to its intersection
>> with my academic background and professional interests.
>>
>> As __cxa_throw is a low-level function provided by the C/C++ ABI
>> (Application Binary Interface) used for throwing exceptions in C/C++
>> programs. It is typically implemented as part of the C/C++ runtime library.
>> This function is invoked when a throw statement is encountered in C/C++
>> code.
>>
>> Throughout my university studies, I have undertaken in-depth coursework in
>> Assembly language. This foundational knowledge has equipped me with a solid
>> understanding of low-level keywords , their significance within the context
>> of compiler design.
>>
>> Furthermore, my academic curriculum has provided me with a comprehensive
>> understanding of core programming concepts, including polymorphism,
>> inheritance, aggregation, data structures and Inter-process communication .
>> I have also gained practical experience in implementing these concepts
>> through various programming assignments and projects.
>>
>> I firmly believe that my academic background, coupled with my enthusiasm
>> for compiler technology  positions me well to contribute meaningfully to
>> the improvement of nothrow detection in GCC. With the guidance and
>> mentorship of experienced professionals ,  I am confident in my ability to
>> navigate the complexities of this project and propose effective solutions.
>>
>> *Fourthly *, As the deadline for submitting proposals for the GSoC 2024
>> program approaches rapidly, I am reaching out to seek your guidance on the
>> essential topics that should be addressed within my proposal for securing
>> an internship position within the GNU Compiler Collection (GCC).
>
> In a general form, it is all described here:
> https://gcc.gnu.org/wiki/SummerOfCode#Application
>
> More information about this project has been given for example at the
> end of https://gcc.gnu.org/pipermail/gcc/2024-March/243512.html (don't
> be confused by the subject, the thread discusses two projects).
>
> Which brings me to the point that , these questions should be directed
> to the mailing list (which I am CCing) where you can reach mentors and
> other people who know more about these things than me.
>
> Good luck,
>
> Martin
>
>
>>
>> Warm regards,
>> M Hamza Nadeem
>>
>> On Mon, Mar 25, 2024 at 9:54 PM M Hamza Nadeem <nadeemmhamza@gmail.com>
>> wrote:
>>
>>> Thanks, I'll check them out.
>>>
>>> On Mon, 25 Mar 2024, 9:50 pm Martin Jambor, <mjambor@suse.cz> wrote:
>>>
>>>> Hello,
>>>>
>>>> On Sun, Mar 24 2024, M Hamza Nadeem via Gcc wrote:
>>>> > Hi Sir / mam,
>>>> >
>>>> >
>>>> > I hope this email finds you well. As an enthusiastic contributor with a
>>>> > strong grasp of C/C++ and familiarity with Rust, I am eager to explore
>>>> > potential projects for Google Summer of Code (GSoC) 2024 within the GNU
>>>> > Compiler Collection (GCC) ecosystem.
>>>>
>>>> we are delighted you found the prospect of contributing to GCC
>>>> interesting.
>>>>
>>>> >
>>>> > With my background in these languages and my passion for advancing
>>>> compiler
>>>> > technology, I believe I could make significant contributions to various
>>>> GCC
>>>> > projects.
>>>> >
>>>> > I would greatly appreciate any guidance on how to proceed further with
>>>> > project selection or any additional insights into the GCC projects
>>>> relevant
>>>> > to my skill set.
>>>>
>>>> Please look again at the "Before you apply" section of our GSoC page at
>>>> https://gcc.gnu.org/wiki/SummerOfCode#Before_you_apply and make sure you
>>>> are
>>>> able to build, install and test GCC.  I strongly suggest that you also try
>>>> generating dumps of the IR of a simple compiled program and stepping
>>>> through
>>>> some function during compilation in a debugger.
>>>>
>>>> Afterwards, look at the suggested projects, try to identify the portion
>>>> of GCC
>>>> source where it needs to be implemented and think about how.  Then email
>>>> us
>>>> back to this mailing list describing your current plan together with any
>>>> technical questions you'd like to have answered to proceed further.
>>>> We'll be
>>>> happy to help.
>>>>
>>>> Good luck,
>>>>
>>>> Martin
>>>>
>>>>