Dmitry Antipov wrote:
Hello all,
I have a question about possible cooperation between the compiler and
hypothetical
garbage collector. Unfortunately, my experience around GCC internals is
too small,
so I would like to ask compiler specialists before re-inventing an ugly
bicycle...
The most non-straightforward garbage collection methods, including, but
not limited to,
the most frequently used generational and incremental techniques,
requires a 'write
barrier' or 'store barrier' - a piece of code which is executed when a
pointer (within
one object, usually) to some another object is written.
People interested by generational GC with write barriers
might be interested in the paper I presented on July 18th 2007 at GCC summit
http://starynkevitch.net/Basile/gccsummit2007-starynkevitch.pdf (a slightly updated form); my (buggy, incomplete) code
is downloadable on my home page eg at http://starynkevitch.net/Basile/basile-ggcc-patches.tgz
I intend to make a branch, as Diego Novillo kindly suggested me (at the GCC
summit), in august 2007.
Given that my copyright assignment is ok (and I already got small patches accepted) what is the way to make branches, in
particular with GPLv3? I don't want to mess with copyrights & license files, so I am waiting a few weeks for these
questions to be settled.
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net | mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***
