From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out2.suse.de (smtp-out2.suse.de [IPv6:2a07:de40:b251:101:10:150:64:2]) by sourceware.org (Postfix) with ESMTPS id 0BC893858D33 for ; Sat, 30 Mar 2024 22:48:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0BC893858D33 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=suse.cz ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 0BC893858D33 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2a07:de40:b251:101:10:150:64:2 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1711838900; cv=none; b=IEZ9GedfFdFDrAbDl59/ahTf9nDQFKiv/iWCI2chw2kMywxoJZhHL33IpzO99NUZxq7KTroyRdUCy0vMGkaSTTykn1woFMwNBO3F0g4wlvWVP3jAZGenVHPPHHerQUPH/BDyVpWkh8d/04Z1ILhUMvWhqBv8v3guo44MtpKHaGo= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1711838900; c=relaxed/simple; bh=5V3hCjHuzfnehb4m+VAizlImfz6hin6CsDGoJcle8NQ=; h=DKIM-Signature:DKIM-Signature:From:To:Subject:Date:Message-ID: MIME-Version; b=bzkRTTz9jA7Qce8ApxVqr1u3k8IB5DAfFntxQHYrI9O7f3Tu6glBOIUWY5H4rm9i4K0DIhwwkHRV/X10YzZZJtAWDE5bMF2c8lRdHjS+XPbKjt7aSLkS0CQd6DrMtE4g/Z0+MWJFbiIrzy81sScftt5zl5vDrnj9vW4YVzQ4QzI= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from imap2.dmz-prg2.suse.org (imap2.dmz-prg2.suse.org [10.150.64.98]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 091995F9D0; Sat, 30 Mar 2024 22:48:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1711838897; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dXWCh+QsmvRJu/Grcm/yKNgIAwUUfMrkfQNpefsQsYE=; b=TFfnzhuz8IvZgIFoPnqxaXgIxtbK+3i9OIXdM1MKw1ROpbcqxkwA/6gRU7ZsYbKDiCrQYt tnrPTDvVApAEsphzbsh5zWubsHpY4Odyc+JfZ3BymHuAbMwR3xacTjtLe/fRWYH5/6US8/ 1abxOF/4kmLCKiZKBgU3UBuiPcE6dog= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1711838897; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dXWCh+QsmvRJu/Grcm/yKNgIAwUUfMrkfQNpefsQsYE=; b=QQF6aksUAyz6bHZ7DUnFnfqCKB15MGIaX8M2dqtPJaJwhq57b3cSibx7ZBDJcduLMy3xD4 2322E6B3LHW+80AQ== Authentication-Results: smtp-out2.suse.de; none Received: from imap2.dmz-prg2.suse.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by imap2.dmz-prg2.suse.org (Postfix) with ESMTPS id F35AE13A90; Sat, 30 Mar 2024 22:48:16 +0000 (UTC) Received: from dovecot-director2.suse.de ([2a07:de40:b281:106:10:150:64:167]) by imap2.dmz-prg2.suse.org with ESMTPSA id UB3vOrCWCGaVRwAAn2gu4w (envelope-from ); Sat, 30 Mar 2024 22:48:16 +0000 From: Martin Jambor To: M Hamza Nadeem Cc: GCC Mailing List Subject: Re: "GSoC" In-Reply-To: References: User-Agent: Notmuch/0.38.2 (https://notmuchmail.org) Emacs/29.3 (x86_64-suse-linux-gnu) Date: Sat, 30 Mar 2024 23:48:12 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -4.30 X-Spamd-Result: default: False [-4.30 / 50.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVRCPT(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_SIGNED(0.00)[suse.cz:s=susede2_rsa,suse.cz:s=susede2_ed25519]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DBL_BLOCKED_OPENRESOLVER(0.00)[gnu.org:url]; FREEMAIL_TO(0.00)[gmail.com]; FUZZY_BLOCKED(0.00)[rspamd.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; NEURAL_HAM_SHORT(-0.20)[-1.000]; RCVD_TLS_ALL(0.00)[]; BAYES_HAM(-3.00)[100.00%] X-Spam-Level: X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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 complet= ed >> 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-d= esign/ >> . >> > > 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=C4=8Dka, >> 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 intersect= ion >> 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 libra= ry. >> 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 so= lid >> understanding of low-level keywords , their significance within the cont= ext >> 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 communicatio= n . >> 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 solution= s. >> >> *Fourthly *, As the deadline for submitting proposals for the GSoC 2024 >> program approaches rapidly, I am reaching out to seek your guidance on t= he >> 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=E2=80=AFPM M Hamza Nadeem >> wrote: >> >>> Thanks, I'll check them out. >>> >>> On Mon, 25 Mar 2024, 9:50 pm Martin Jambor, 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 wit= h a >>>> > strong grasp of C/C++ and familiarity with Rust, I am eager to explo= re >>>> > 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 vari= ous >>>> GCC >>>> > projects. >>>> > >>>> > I would greatly appreciate any guidance on how to proceed further wi= th >>>> > 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 y= ou >>>> 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 ema= il >>>> us >>>> back to this mailing list describing your current plan together with a= ny >>>> technical questions you'd like to have answered to proceed further. >>>> We'll be >>>> happy to help. >>>> >>>> Good luck, >>>> >>>> Martin >>>> >>>>