From: Juan Scerri <juan.scerri.21@um.edu.mt>
To: gcc@gcc.gnu.org
Subject: Re: GSoC (Make cp-demangle non-recursive)
Date: Sat, 26 Feb 2022 17:31:04 +0100 [thread overview]
Message-ID: <CACJSivsLe4_+cHXe6=yJWx501r5ZkA+e1EYviaH7pOg9+S0CcQ@mail.gmail.com> (raw)
In-Reply-To: <CACJSivv=BmcxsSoM8o8q_82VQ9LDSRC-2_HBsb_AowP+Scir7A@mail.gmail.com>
I have just realised that I have a typo.
I meant to say 'do not hesitate'.
Regards,
Juan Scerri
On Sat, 26 Feb 2022 at 11:34, Juan Scerri <juan.scerri.21@um.edu.mt> wrote:
> To whom this may concern,
>
> Firstly, I will introduce myself. I am Juan Scerri and I am a student at
> the University of Malta studying Computer Science and Mathematics for my
> undergraduate degree.
> I am currently in my first year of studies, which is technically my first
> formal introduction to GNU/Linux. However, I have been using GNU/Linux for
> over a year. I am
> mostly interested in programming which involves compilers, operating
> systems and things of a similar sort.
>
> I have looked at the selected project ideas by the GCC team and one of the
> problems which has caught my attention is making cp-demangle non-recursive.
> I am interested in this particular problem because as stated in the
> "Before you apply" section it is one of the selected problems which do not
> require extensive
> knowledge of the compiler theory (which I will be doing in my 3rd year of
> studies). However, I do understand the aim of the project.
>
> Any guidance would be much appreciated.
>
> If I was no clear in any way do hesitate to contact me.
>
> Regards,
> Juan Scerri
>
next prev parent reply other threads:[~2022-02-26 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 10:34 Juan Scerri
2022-02-26 16:31 ` Juan Scerri [this message]
2022-03-02 18:37 ` Martin Jambor
[not found] ` <CACJSivvYgNG+C2Y5ph=4yv5y0iaV+Ak7=vh3FGD7W6eQADxk9w@mail.gmail.com>
2022-03-09 16:15 ` Martin Jambor
2022-03-27 12:21 Juan Scerri
2022-04-07 15:24 ` 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='CACJSivsLe4_+cHXe6=yJWx501r5ZkA+e1EYviaH7pOg9+S0CcQ@mail.gmail.com' \
--to=juan.scerri.21@um.edu.mt \
--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).