public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Laurynas Biveinis <laurynas.biveinis@gmail.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [gc-improv] Copy current trunk to branch
Date: Thu, 20 Jan 2011 05:50:00 -0000	[thread overview]
Message-ID: <AANLkTimKTBG=OAezO=v3MKWoMF8X6fxj49sstJsBjfUu@mail.gmail.com> (raw)
In-Reply-To: <20110119225145.GK6247@codesourcery.com>

2011/1/20 Nathan Froyd <froydnj@codesourcery.com>:
> On Wed, Jan 19, 2011 at 03:29:47PM +0200, Laurynas Biveinis wrote:
>> I am re-using my merged gc-improv branch for my next memory management
>> project, which is moving RTL out of GC and, time permitting, better GC
>> implementation. I hope to merge it during 4.7 stage 1.
>
> This is excellent!  Would you mind explaining what your plan is?
>

- Move RTL back to obstacks: global, per-function, scratch, maybe a
few per-pass obstacks too. My work so far is based on Bernd Schmidt's
patch [1]. Also this will enable quite a few cleanups: in gengtype,
removal a lot of GTY markers in backends that only serve PCH.
- Merge to trunk.
- Add an object type tag to all GC allocated objects, this should be
trivial now that GC allocation is type-strict.
- Then the "normal" GC implementation techniques: incremental,
copying, generational etc. all become doable. Implement, measure
performance, merge, repeat.

Currently I do not plan to remove the limitation that collection
happens only when invoked explicitly with ggc_collect(). That would
require solving the issue of GC roots on stack in one way or another.

[1] - http://gcc.gnu.org/ml/gcc-patches/2010-08/msg00655.html

-- 
Laurynas

  reply	other threads:[~2011-01-20  4:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 14:29 Laurynas Biveinis
2011-01-19 18:47 ` Basile Starynkevitch
2011-01-20  5:34   ` Laurynas Biveinis
2011-01-20  6:10     ` Basile Starynkevitch
2011-01-20  7:59       ` Laurynas Biveinis
2011-01-20  0:20 ` Nathan Froyd
2011-01-20  5:50   ` Laurynas Biveinis [this message]
2011-01-20 10:14     ` Paolo Bonzini
2011-01-20 10:15       ` Laurynas Biveinis
2011-01-20 11:40         ` Paolo Bonzini
2011-01-20 14:27     ` Richard Kenner
2011-01-21  5:04       ` Laurynas Biveinis
2011-01-21 12:47         ` Richard Kenner
2011-01-22 14:15     ` Basile Starynkevitch
2011-01-23 21:54     ` Bernd Schmidt
2011-01-20 10:02 ` Laurynas Biveinis
2011-01-20 15:54   ` NightStrike
2011-01-21  5:05     ` Laurynas Biveinis

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='AANLkTimKTBG=OAezO=v3MKWoMF8X6fxj49sstJsBjfUu@mail.gmail.com' \
    --to=laurynas.biveinis@gmail.com \
    --cc=froydnj@codesourcery.com \
    --cc=gcc-patches@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).