From: Nathan Sidwell <nathan@acm.org>
To: Eric Gallager <egall@gwmail.gwu.edu>, nick <xerofoify@gmail.com>
Cc: Richard Biener <rguenther@suse.de>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: GSOC Proposal
Date: Mon, 01 Apr 2019 11:47:00 -0000 [thread overview]
Message-ID: <958dc17c-6e84-c12a-b1d1-e7c92f3cb02d@acm.org> (raw)
In-Reply-To: <CAMfHzOvN=5ipdwWGe2DJ7CZMNE6RoZuyzy-HT6Jr5bSLPqH5Mg@mail.gmail.com>
On 4/1/19 1:24 AM, Eric Gallager wrote:
> On 3/29/19, nick <xerofoify@gmail.com> wrote:
>> Seems your right touching the complete garbage collector is too much. I'm
>> just looking at the users of the garbage collector and it seems one of the
>> major ones is pre compiled headers.
>>
>
> The thing about pre-compiled headers is that I seem to remember some
> GCC devs saying they wanted to rip out pre-compiled headers completely
> once the C++ modules branch is merged, so I'm not sure if it's worth
> putting that much work into something that might be removed soon,
> anyways... I'm pretty sure Nathan Sidwell is the main person working
> on the C++ modules branch, so I'm cc-ing him.
The use of the GC machinery for PCH is needed by the front ends and is
orthogonal to that for GC during code generation.
nathan
--
Nathan Sidwell
next prev parent reply other threads:[~2019-04-01 11:47 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
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 [this message]
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=958dc17c-6e84-c12a-b1d1-e7c92f3cb02d@acm.org \
--to=nathan@acm.org \
--cc=egall@gwmail.gwu.edu \
--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).