public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aniket Agarwalla <aniketagarwalla37@gmail.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: gcc@gcc.gnu.org
Subject: Re: Regarding GSOC
Date: Tue, 26 Mar 2019 18:29:00 -0000	[thread overview]
Message-ID: <CANO+YERGbjXL+CZA=xgoQHtTi5HpHRZhXm74h35SYfo5GwEifg@mail.gmail.com> (raw)
In-Reply-To: <ri6h8bpwl7t.fsf@suse.cz>

Thank you, I will do that.

On Tue, Mar 26, 2019, 11:51 PM Martin Jambor <mjambor@suse.cz> wrote:

> Hi Aniket,
>
> On Mon, Mar 25 2019, Aniket Agarwalla wrote:
> > Hello Sir,
> >
> > I am interested in working with you in your shortlisted projects on Gsoc
> > 2019 namely
> > "Add new math.h and complex.h functions as built-ins".
>
> we are already in fairly advanced stage of putting together a proposal
> for the same project with Tejas Joshi.  You can of course try to submit
> a better one but it will be difficult.  Or you just have about time to
> switch and attempt a different project idea.
>
> > I would like to add that I have a good mathematical background and have
> > been doing competitive programming for years now.So I think I can work
> hard
> > on this project and complete the project as per the organization
> > requirements. I also wanted to know what more I can do or submit a
> proposal
> > to get a chance to work with your organization.
>
> Please look again at the "Before you apply" section of our GSoC wiki
> page at 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.
>
> Then find bits of GCC that are relevant to your selected project and
> continue exploring like above.  If you have any specific questions, feel
> free to ask again here on the mailing list.
>
> Good luck,
>
> Martin
>

  reply	other threads:[~2019-03-26 18:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25 14:14 Aniket Agarwalla
2019-03-26 18:21 ` Martin Jambor
2019-03-26 18:29   ` Aniket Agarwalla [this message]
     [not found] <FF02519E-D1EA-43F9-86BA-AF6EFDECC8BE@hxcore.ol>
2023-03-13 13:13 ` Megha Raj
2023-03-14 17:25   ` Martin Jambor
     [not found]     ` <CACstDaEpYbNWR2ABw6gUD+jvQnygno7wJhJYDmux2_o+qD6YnQ@mail.gmail.com>
2023-03-21 20:19       ` 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='CANO+YERGbjXL+CZA=xgoQHtTi5HpHRZhXm74h35SYfo5GwEifg@mail.gmail.com' \
    --to=aniketagarwalla37@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    /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).