Nevertheless: maybe it would be feasible to do all second gen
gc in a dedicated thread and force a minor gc before passing data
between threads? Would it?
Unfortunately, execution and garbage collection are tightly interleaved
in the cheney-on-the-mta model.
But the idea is intriguing.
Felix scripsit:
Unfortunately, execution and garbage collection are tightly interleaved
in the cheney-on-the-mta model.
Minor collection is, but major collection could be run in a separate
thread so that it can run concurrently (even on a second core) with the
rest of the program. As it
*cringe*
This will certainly expose what is and is not thread-safe within
Chicken. I've worked with a /team/ in implementing such behaviour in the
Unreal engine, albeit a frankenengine of sorts, and with three dedicated
programmers the endeavour required about a month. But we had the benefit
From: John Cowan co...@mercury.ccil.org
Subject: Re: [Chicken-users] Best way to share memory between C and Chicken
Date: Mon, 6 May 2013 08:21:34 -0400
Felix scripsit:
Unfortunately, execution and garbage collection are tightly interleaved
in the cheney-on-the-mta model.
Minor
