From: Richard Biener <richard.guenther@gmail.com>
To: nick <xerofoify@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>, richard Biener <rguenther@suse.de>
Subject: Re: GSOC Proposal
Date: Thu, 28 Mar 2019 08:59:00 -0000 [thread overview]
Message-ID: <CAFiYyc0AbLoU6=OD6D0G=nRbtVSdujrQNBH-miNWiF5QW2kijA@mail.gmail.com> (raw)
In-Reply-To: <4327491a-395b-bee0-145a-eddd8f64b0ba@gmail.com>
On Wed, Mar 27, 2019 at 6:31 PM nick <xerofoify@gmail.com> wrote:
>
> Greetings All,
>
> I've already done most of the work required for signing up for GSoC
> as of last year i.e. reading getting started, being signed up legally
> for contributions.
>
> My only real concern would be the proposal which I started writing here:
> https://docs.google.com/document/d/1BKVeh62IpigsQYf_fJqkdu_js0EeGdKtXInkWZ-DtU0/edit?usp=sharing
>
> The biography and success section I'm fine with my bigger concern would be the project and roadmap
> section. The roadmap is there and I will go into more detail about it in the projects section as
> need be. Just wanted to known if the roadmap is detailed enough or can I just write out a few
> paragraphs discussing it in the Projects Section.
I'm not sure I understand either the problem analysis nor the project
goal parts. What
shared state with respect to garbage collection are you talking about?
Richard.
> Any other comments are welcome as well as I write it there,
> Nick
next prev parent reply other threads:[~2019-03-28 8:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 17:31 nick
2019-03-28 8:59 ` Richard Biener [this message]
2019-03-28 13:38 ` nick
2019-03-29 9:08 ` Richard Biener
2019-03-29 14:28 ` nick
2019-03-29 17:00 ` nick
2019-04-01 5:25 ` Eric Gallager
2019-04-01 11:47 ` Nathan Sidwell
2019-04-01 9:56 ` Richard Biener
2019-04-01 13:39 ` nick
2019-04-01 13:48 ` Richard Biener
2019-04-01 14:14 ` nick
2019-04-03 11:30 ` Richard Biener
2019-04-03 15:21 ` nick
2019-04-05 10:25 ` Richard Biener
2019-04-05 16:11 ` nick
2019-04-07 9:31 ` Richard Biener
2019-04-07 15:40 ` nick
2019-04-08 7:30 ` Richard Biener
2019-04-08 13:19 ` nick
2019-04-08 13:42 ` Richard Biener
2019-04-08 14:17 ` nick
-- strict thread matches above, loose matches on Subject: below --
2022-04-18 17:32 GSoC Proposal Abhigyan Kashyap
2018-03-21 18:39 GSOC proposal Ismael El Houas Ghouddana
2018-03-26 13:31 ` Martin Jambor
2013-03-17 6:02 GSoC Proposal Sai kiran
2013-03-21 18:01 ` Benjamin De Kosnik
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='CAFiYyc0AbLoU6=OD6D0G=nRbtVSdujrQNBH-miNWiF5QW2kijA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=xerofoify@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).