On Tue, Apr 21, 2015 at 09:47:50AM -0400, co...@ccil.org wrote:
Peter Bex scripsit:
That's right. That's why I described it as an extension of the nursery:
it isn't actually stored on the stack,
So it could be allocated in the heap or simply as a global array.
Since there is only one
Hi,
On Tue, 7 Apr 2015 11:32:39 +0200 Peter Bex pe...@more-magic.net wrote:
If anyone wants to add it to the chicken-benchmark repo, I would
recommend removing the writing of the output file, as that's really
not where the bottleneck is, and writing a file isn't very nice in a
benchmark
Two very simple cleanup patches.
Thanks - signed off and pushed.
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
The scratch area is seen as an extension of the nursery: the
C_demand() and C_stack_probe() checks will add the size of the scratch
space to the stack's size, and trigger a minor GC when the sum of the
two exceeds the maximum nursery size.
So this is just a heuristic, as the data in
Peter Bex scripsit:
That's right. That's why I described it as an extension of the nursery:
it isn't actually stored on the stack,
So it could be allocated in the heap or simply as a global array.
Since there is only one at a time, and its size is fixed, a global array
would make sense to me,
On Tue, Apr 21, 2015 at 12:11:18PM +0200, Felix Winkelmann wrote:
The scratch area is seen as an extension of the nursery: the
C_demand() and C_stack_probe() checks will add the size of the scratch
space to the stack's size, and trigger a minor GC when the sum of the
two exceeds the
