Hi Noah,
Noah Lavine skribis:
> As long as we're pinging people for 2.0.5, I don't think this patch
> ever got pushed. :-)
Apparently it was applied as 4eb286127c41e67eb90ef1b69f61f613bcd830b2.
Thanks,
Ludo’.
Hello,
As long as we're pinging people for 2.0.5, I don't think this patch
ever got pushed. :-)
I can't build master right now. This is partly my fault for doing so
little sysadmin work that I still have libgc 7.1, but I still think
this one should really, really be in 2.0.5 if the GC changes wil
On Thu 08 Dec 2011 16:46, "Chris K. Jester-Young" writes:
> Alas, part of that diff also breaks libgc 7.1 (which is the version that
> Debian currently has packaged), which lack the unmapping functions.
> Here's my diff to make it work again.
Thanks for the patch! In the future a git-format-pat
On Fri, Dec 02, 2011 at 12:09:12AM +0100, Andy Wingo wrote:
> One change was to make GC run more often when a process is growing, in
> terms of resident memory size. This seems to be a good idea in general.
>
> The other was to add a function that users can call to note
> non-gc-managed allocatio
Hi,
I recently poked some GC-related things in stable-2.0 and master.
One change was to make GC run more often when a process is growing, in
terms of resident memory size. This seems to be a good idea in general.
The other was to add a function that users can call to note
non-gc-managed allocat
