From: SAYAN MANDAL <mandalsayan113@gmail.com>
To: gcc@gcc.gnu.org
Subject: GSoC contributor for GCC
Date: Thu, 31 Mar 2022 10:19:42 +0530 [thread overview]
Message-ID: <CAGLw_qF3RvpWo_jLTLQxOm3tiW8Gzod1oGwTjb1Ka2vWj=RTnA@mail.gmail.com> (raw)
Sir,
I am a second year student from VIT, Vellore willing to participate in GSoC
and contribute to GCC. I am really sorry for this late application. The
reasons for choosing it are as follows
1. I am using GCC and GDB for C, C++ and NASM programming and I am
comfortable with most of the features of GCC
2. Since it has been a great asset in my learning journey, I want to
contribute to its development
3. I am willing to learn any additional compiler technologies needed for it
I am mostly interested in bypassing assembler in
1. Generating LTO object files
2. Making cp-demangle non-recursive
Please let me know what I need to do in order to become a part of the GCC
development team.
SAYAN MANDAL
918617005956
next reply other threads:[~2022-03-31 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 4:49 SAYAN MANDAL [this message]
2022-04-06 16:45 ` 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='CAGLw_qF3RvpWo_jLTLQxOm3tiW8Gzod1oGwTjb1Ka2vWj=RTnA@mail.gmail.com' \
--to=mandalsayan113@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).