public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Benjamin Priour <priour.be@gmail.com>, gcc@gcc.gnu.org
Subject: Re: [GSoC] Interest in project ideas and request for a small patch
Date: Wed, 15 Mar 2023 12:51:20 -0400	[thread overview]
Message-ID: <8b61de46ace46c52964dd41b236c0576fd8f2d6c.camel@redhat.com> (raw)
In-Reply-To: <CAKiQ0GH1giQfiqZy-5A9AMDih6UhTvQLjfQnafUNuqom10B4GQ@mail.gmail.com>

On Wed, 2023-03-15 at 17:35 +0100, Benjamin Priour via Gcc wrote:
> Hi,
> I'm Benjamin and I have been looking around the mail list and the
> code base
> since last December, where I had to write a simple Deca compiler
> within a
> month as a team. Next paragraph is me introducing myself -ranting
> really-
> for too long.
> 
> I am from France, in my Computer science master's first year, and
> very much
> interested in compilers and operating systems. I was already
> considering
> applying for the GSoC, but felt rather intimidated by the scale of it
> so I
> kind of forgot about it until last week my university housed a
> gathering
> event for companies to promote internships.
> Few of them appealed to me, while my teacher cheered for me to try
> and
> reach you out, so here I am.

Hi Benjamin, thanks for reaching out.

Don't let feeling intimdated put you off.  GCC is a big project, but we
don't expect newcomers to understand everything from the beginning
(I've been working on it for about 10 years now, and I'm still
discovering areas of the code I hadn't see before).

> 
> Hence, even if it's two weeks late, I would like to express my
> interest in
> contributing to the project ideas listed below, and request for small
> patch
> I could work on.

I don't think you're late; the timetable here:
  https://developers.google.com/open-source/gsoc/timeline
says that we're still in "discussing application ideas" phase, and the
deadline for actually applying is April 4th (IIRC Google enforces that
one strictly).

> 
> - [Extend the static analysis pass] is the one I feel the most
> confident
> in, but I see it is already quite envied.

Note that there could be more that one project involving the analyzer;
the wiki page lists several ideas (and our bugzilla instance has plenty
of other ideas for new features).

I would be mentoring analyzer projects.  I mentored two different
analyzer projects last year; both students did well.

[...snip other project ideas...]
> 
> I have experience working on a Python debugger during my previous
> internship, as well as the full-time compiler project I did last
> January.
> From those experiences, reading Crafting Interpreters (R.Nystrom) and
> my
> language theory courses, I'm certain I will enjoy contributing to
> this.

It sounds like you have a lot of relevant knowledge already.

> 
> Oof, finally braced myself to reach you out, sadly almost too late,
> but I
> just got a boulder-sized weight off my shoulders.
> Thanks in advance! -  I tried to keep it short.
> 

Hope the above is helpful; thanks for reaching out
Dave


      reply	other threads:[~2023-03-15 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 16:35 Benjamin Priour
2023-03-15 16:51 ` David Malcolm [this message]

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=8b61de46ace46c52964dd41b236c0576fd8f2d6c.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=priour.be@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).