From: Martin Jambor <mjambor@suse.cz>
To: Megha Raj <megharajmathur0224@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Regarding GSOC
Date: Tue, 14 Mar 2023 18:25:31 +0100 [thread overview]
Message-ID: <ri6r0tr5jp0.fsf@suse.cz> (raw)
In-Reply-To: <CACstDaHt91ZDN2mODtBEWcZhcWzeoKFm3w5qbo2h+JTFKOHPJg@mail.gmail.com>
Hello,
On Mon, Mar 13 2023, Megha Raj via Gcc wrote:
> Respected sir/mam,
>
> Actually I want to know what are skills you desire to have in the members
> of your organization as I’m aware with c &c++ so, can you please let me
> know other than this what knowledge should I know for getting selected in
> your franchise in deep
We are delighted you found contributing to GCC interesting.
Apart from C/C++ coding skills, most projects require some rudimentary
theoretical background in compilers.
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.
Afterwards, look at a suggested idea, try to identify the portion of GCC
source which is involved and email us back to the mailing list,
describing the idea and (often with help from the community) what is
your plan to address it. Also, we'll be happy to help with any specific
GCC development issues you may encounter.
Good luck,
Martin
next prev parent reply other threads:[~2023-03-14 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FF02519E-D1EA-43F9-86BA-AF6EFDECC8BE@hxcore.ol>
2023-03-13 13:13 ` Megha Raj
2023-03-14 17:25 ` Martin Jambor [this message]
[not found] ` <CACstDaEpYbNWR2ABw6gUD+jvQnygno7wJhJYDmux2_o+qD6YnQ@mail.gmail.com>
2023-03-21 20:19 ` Martin Jambor
2019-03-25 14:14 Aniket Agarwalla
2019-03-26 18:21 ` Martin Jambor
2019-03-26 18:29 ` Aniket Agarwalla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ri6r0tr5jp0.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=gcc@gcc.gnu.org \
--cc=megharajmathur0224@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).