From: "tmpod" <tom@tmpod.dev>
To: <gcc@gcc.gnu.org>
Subject: [GSoC] Interest in applying
Date: Sun, 31 Mar 2024 12:57:24 +0000 [thread overview]
Message-ID: <D07YAXOLQOAW.1KDO43VZVT1RH@tmpod.dev> (raw)
Hello,
I am a Computer Science student, currently taking a Master's degree in
Portugal's top university. I have a strong passion for algorithms, data
structures and high performance computing, having participated in many
programming contests (nationals, SWERC, Google's now defunct
competitions, etc) too. I have also some experience in contributing to
open-source and working in software development teams.
C and C++ are the languages I've used the most, always compiled with
GCC. My fascination with this area of computer science, and especially
with GCC's details, has been present since an early age, so this Google
program felt like the perfect opportunity to act and learn more!
After carefully reading your approved ideas page, the ones that stand
out more to me are:
* Improving OpenACC support
* Extending the static analysis pass (for format strings, in particular)
* Improving nothrow detection
I have read the "Before you apply" and completed some of the steps
outlined, and will do so as well for the remaining, tomorrow.
I am aware of the very tight deadline and that it may be hard to write a
community-backed proposal now, but unfortunately I was only made aware
of Google's program a couple of days ago. Still, I'm going to try my
best to write a quality proposal until Tuesday.
If you have any suggestions, please let me know!
I'd love to further discuss these with you.
Kind regards,
~tmpod
PS: To all celebrating Easter (and not hehe!), I hope you have wonderful Sunday.
next reply other threads:[~2024-03-31 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 12:57 tmpod [this message]
2024-04-02 15:10 ` 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=D07YAXOLQOAW.1KDO43VZVT1RH@tmpod.dev \
--to=tom@tmpod.dev \
--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).