From: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
To: Prateek Kalra <prateekkalra2010@gmail.com>, ak@linux.intel.com
Cc: gcc@gcc.gnu.org
Subject: Re: GCC GSOC Participation
Date: Tue, 06 Mar 2018 22:22:00 -0000 [thread overview]
Message-ID: <CAAgBjMnpoBR8AVS1Rc3+sQPstSW9Yks5b4Rwo-=4FFH7HnuzxQ@mail.gmail.com> (raw)
In-Reply-To: <CAHoX0C=fO3PkdccK_y_GvNa8AsN-TY6DLdJK3s-Z_dNshDmOHg@mail.gmail.com>
CCing Andi Kleen, mentor of this project.
Regards,
Prathamesh
On 3 March 2018 at 16:22, Prateek Kalra <prateekkalra2010@gmail.com> wrote:
> Hello GCC Community,
> My name is Prateek Kalra.I am pursuing integrated dual
> degree(B.tech+M.tech) in Computer Science Software Engineering,from Gautam
> Buddha University,Greater Noida.I am currently in 8th semester of the
> programme.
> I have experience in competitive programming with C++.Here's my linkedin
> profile:
> https://www.linkedin.com/in/prateek-kalra-6a40bab3/.
> I am interested in GSOC project "Implement a fuzzer leveraging GCC
> extensions".
> I had opted compiler design as one of the course subjects in the previous
> semester and was able to secure an 'A' grade at the end of the semester.
> I have theoretical knowledge of fuzz testing and csmith,that how the random
> C programs are generated to check the compiler bugs and I am very keen to
> work under this project.
> I request you to guide me to progress through the process.I would really
> appreciate if you could mentor me with the further research of this project
> idea.
> Regards,
> Prateek
next prev parent reply other threads:[~2018-03-06 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 10:52 Prateek Kalra
2018-03-06 22:22 ` Prathamesh Kulkarni [this message]
2018-03-07 16:00 ` Andi Kleen
2018-03-06 22:44 ` Martin Jambor
2018-03-07 16:01 ` Andi Kleen
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='CAAgBjMnpoBR8AVS1Rc3+sQPstSW9Yks5b4Rwo-=4FFH7HnuzxQ@mail.gmail.com' \
--to=prathamesh.kulkarni@linaro.org \
--cc=ak@linux.intel.com \
--cc=gcc@gcc.gnu.org \
--cc=prateekkalra2010@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).