public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* getting start with GSoC
@ 2024-02-16 21:15 Nada Elsayed
  2024-03-01 13:03 ` Martin Jambor
  0 siblings, 1 reply; 2+ messages in thread
From: Nada Elsayed @ 2024-02-16 21:15 UTC (permalink / raw)
  To: gcc

[-- Attachment #1: Type: text/plain, Size: 531 bytes --]

Hello All,
I am Nada Elsayed, A fresh graduate from computer engineering at Cairo
University.
I have good knowledge in C/C++, and a basic knowledge in compilers. als I
am interested in contributing to the GCC this year; I am interested in "*Extend
the static analysis pass" *projects or "*Improve nothrow detection in GCC" *
project*.*

Till now I have built the code and I am trying to understand it more. So
what should I do now? Also, are bugs in https://gcc.gnu.org/wiki/EasyHacks good
beginning or not?

Regards,
Nada Elsayed

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: getting start with GSoC
  2024-02-16 21:15 getting start with GSoC Nada Elsayed
@ 2024-03-01 13:03 ` Martin Jambor
  0 siblings, 0 replies; 2+ messages in thread
From: Martin Jambor @ 2024-03-01 13:03 UTC (permalink / raw)
  To: Nada Elsayed, gcc

Hello,

On Fri, Feb 16 2024, Nada Elsayed via Gcc wrote:
> Hello All,
> I am Nada Elsayed, A fresh graduate from computer engineering at Cairo
> University.

welcome, we are delighted you found contributing to GCC interesting.

> I have good knowledge in C/C++, and a basic knowledge in compilers. als I
> am interested in contributing to the GCC this year; I am interested in "*Extend
> the static analysis pass" *projects

Any particular one?

> or "*Improve nothrow detection in GCC" project*.*
>
> Till now I have built the code and I am trying to understand it more.

Good, this is the all-important first step.

> So what should I do now?

"Trying to understand it more" is exactly the correct thing to.  You
also need to locate which of the bits within GCC are relevant to the
project(s) you are interested in and start thinking what and where needs
to be changed in order to implement it.

If you have specific questions as you go about it, feel free to ask on
this mailing list or on IRC.

> Also, are bugs in https://gcc.gnu.org/wiki/EasyHacks good
> beginning or not?

The page itself is unfortunately very outdated.  However, the link to
the bugzilla search near its top might still be useful.

While it definitely helps, we do not strictly require applicants to do
any "easy hacks" or patch submissions prior to application.  The main
reason is that there are not as many opportunities for truly easy fixes
and improvements as other projects might have.  Still, feel free to
pursue one, it can only help!

Good luck!

Martin

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-03-01 13:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-16 21:15 getting start with GSoC Nada Elsayed
2024-03-01 13:03 ` Martin Jambor

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).