public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Suraj Kadapa <surajkadapa103@gmail.com>
To: gcc@gcc.gnu.org
Subject: Contributor to the GSoC of 2024
Date: Thu, 22 Feb 2024 00:04:11 +0530	[thread overview]
Message-ID: <CAAM8LWHsNFJnJnQ+0Wvtm0Cwwz2QU3v6AH2ue2=Nq0JwWMu+pw@mail.gmail.com> (raw)

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

Hello,

I am an undergraduate student with an extensive experience in computers
from an early age, but most of my work has been limited to arduinos, and
raspberry pi's. I have been intrigued with compilers, architecture and low
level programming in the past few years. I have experience with ARM
assembly and a little bit of x86 too. I have worked towards building
bootloaders and teaching it to my fellow peers too. I've constructed a
process virtual machine modeled after the LC-3 architecture and am
presently focused on developing a basic emulator for RISC-V. Both of the
previously mentioned projects are being done in C, and I have extensive
experience in C. I really want to know how the GNU Compiler collection
works under the hood and this is a really good opportunity for me to
explore and learn.

Please reach out to me on what needs to be done to be accepted as a
contributor to the GSoC program under the GNU organization, I would love to
work on any of the projects mentioned in the wiki(would prefer some easy
ones though, since I am not that deep yet).

My github will be linked below, and I hope to hear from you soon!
https://github.com/surajkadapa

This is my first time writing for the GSoC program, so I am not really sure
if this is how you reach out to organizations in this capacity. Please
excuse any potential oversights as I navigate this process.

Regards,
Suraj

             reply	other threads:[~2024-02-21 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 18:34 Suraj Kadapa [this message]
2024-03-01 13:49 ` Martin Jambor

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='CAAM8LWHsNFJnJnQ+0Wvtm0Cwwz2QU3v6AH2ue2=Nq0JwWMu+pw@mail.gmail.com' \
    --to=surajkadapa103@gmail.com \
    --cc=gcc@gcc.gnu.org \
    /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).