From: Martin Jambor <mjambor@suse.cz>
To: Maria Kalikas <mariakalikas@gmail.com>, gcc@gcc.gnu.org
Cc: jason@redhat.com, nathan@acm.org
Subject: Re: GSoC (Making C++ concepts conform to the current standard)
Date: Wed, 14 Mar 2018 17:23:00 -0000 [thread overview]
Message-ID: <ri61sgm4lms.fsf@suse.cz> (raw)
In-Reply-To: <CA+=Vy4uExOggV9oa9RDmeRDp-L=KDnkvQ-iiSyBNokedbEj7+g@mail.gmail.com>
Hello Maria,
On Wed, Mar 14 2018, Maria Kalikas wrote:
> Hello anyone this concerns,
>
> My name is Maria Kalikas and I am a senior majoring in Computer Science at
> The University of Akron.
>
> My familiarity and continuous reading of the C++ Standard has encouraged me
> to extend the previously developed support for concepts in GCC. I want to
> modify the implementation to conform with the current specification in the
> C++ Standard. I am curious to know if this would be a good project to
> propose for Google Summer of Code and am interested in finding a mentor.
I personally do not know what the status of C++ concept implementation
is, how much it differs from the current standard is or whether making
it more up to date would make a good GSoC project. Jason, Nathan, what
do you think? (And if so, would you be willing to be a mentor? Can you
think of someone else?)
Martin
>
> I took a Compiler Design course in Spring 2017 where I designed a compiler
> for a C-like programming language. My implementation is written in C++.
> Since completing the course, I became familiar with Clang and LLVM and am
> currently completing a capstone project where I am creating a virtual
> machine to implement the C++ abstract machine using LLVM instructions and
> rewriting the conversions, expressions and declarations specified in the
> C++ Standard as three address code instructions.
>
> I look forward to any responses and feedback.
>
> Thank you,
>
> Maria Kalikas
next prev parent reply other threads:[~2018-03-14 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 9:49 GSoC Maria Kalikas
2018-03-14 17:23 ` Martin Jambor [this message]
2018-03-14 17:26 ` GSoC (Making C++ concepts conform to the current standard) Nathan Sidwell
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=ri61sgm4lms.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=mariakalikas@gmail.com \
--cc=nathan@acm.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).