Hi,
On 13-09-2010, Eray Ozkural examach...@gmail.com wrote:
Hi there,
What exactly are the requirements for substituting the current GC with
another, preferably non-locking, GC? Any pitfalls I wouldn't see just
reading the code?
The GC is deeply interacting with the the rest of the
On Mon, Sep 13, 2010 at 10:57 AM, Sylvain Le Gall sylv...@le-gall.netwrote:
Hi,
On 13-09-2010, Eray Ozkural examach...@gmail.com wrote:
Hi there,
What exactly are the requirements for substituting the current GC with
another, preferably non-locking, GC? Any pitfalls I wouldn't see just
On 13-09-2010, Eray Ozkural examach...@gmail.com wrote:
On 13-09-2010, Eray Ozkural examach...@gmail.com wrote:
Hi there,
What exactly are the requirements for substituting the current GC with
another, preferably non-locking, GC? Any pitfalls I wouldn't see just
reading the code?
On Mon, Sep 13, 2010 at 3:22 PM, Sylvain Le Gall sylv...@le-gall.netwrote:
On 13-09-2010, Eray Ozkural examach...@gmail.com wrote:
On 13-09-2010, Eray Ozkural examach...@gmail.com wrote:
Hi there,
What exactly are the requirements for substituting the current GC with
another,
On 13-09-2010, Eray Ozkural examach...@gmail.com wrote:
--===0758070018==
Content-Type: multipart/alternative; boundary=000e0cd18672fce48b049024b79e
--000e0cd18672fce48b049024b79e
Content-Type: text/plain; charset=ISO-8859-1
On Mon, Sep 13, 2010 at 3:22 PM, Sylvain Le Gall
Hi Eray,
Retrofitting a new multicore-friendly GC onto OCaml is difficult for two
main reasons:
1. You want plug-and-play GCs but the OCaml compiler is tightly coupled to
the old GC (although OC4MC has decoupled them!).
2. Recovering similar performance whilst reusing the same data
Other GC algorithm for Java/C# often made the assumption of long-living
objects with mutation. This is not the case for OCaml.
They do favour mutation and, consequently, have cheaper write barriers but
both the JVM and CLR use pointer-bumping minor heaps for the first nursery
generation to
On Tue, Sep 14, 2010 at 12:25 AM, Jon Harrop
jonathandeanhar...@googlemail.com wrote:
Hi Eray,
Retrofitting a new multicore-friendly GC onto OCaml is difficult for two
main reasons:
1. You want plug-and-play GCs but the OCaml compiler is tightly coupled to
the old GC (although OC4MC has