public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Igor Putovny <igorputovny@gmail.com>
To: gcc@gcc.gnu.org
Subject: GSoC 2023
Date: Mon, 27 Mar 2023 15:05:08 +0200	[thread overview]
Message-ID: <CAMq0OktNtXuQZt47ZukXYERt_+UW--c93rSxN2tQEmVq2U0BbA@mail.gmail.com> (raw)

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

Dear all,

I am a student of computer science and I was thinking about applying for
Google Summer of Code 2023. Naturally, I wanted to reach out to you before
applying for GCC projects.

From selected topics you are interested in, several grabbed my attention:
1. Bypass assembler when generating LTO object file
2. Extend the static analysis pass
3. Rust Front-End: HIR Dump
4. Rust Front-End: Improving user errors

I have to admit that I feel a bit intimidated by projects of "hard
difficulty", because I have seen how hard it is to find your way in a large
codebase (which GCC definitely is).

Therefore, I would like to ask you for your opinion about these topics and
the level of theoretical/practical experience with compilers you are
expecting.

As for the languages used, I have advanced knowledge of C and intermediate
knowledge of C++.

Thank you very much for your time.

Best regards,
Igor Putovný

             reply	other threads:[~2023-03-27 13:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 13:05 Igor Putovny [this message]
2023-03-29 16:24 ` Martin Jambor
  -- strict thread matches above, loose matches on Subject: below --
2023-03-27 23:26 Igor Putovny
2023-03-19  6:01 ANKESH PANDEY .
2023-03-21 20:40 ` 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=CAMq0OktNtXuQZt47ZukXYERt_+UW--c93rSxN2tQEmVq2U0BbA@mail.gmail.com \
    --to=igorputovny@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).