Would there be any objection to cutting the size of memory required by
t/pmc/resizablebooleanarray_17.pasm in half? As is, it's sometimes
hitting PANIC("Out of mem") for me. I don't think there's anything
fundamental about the number 1,100,000 used in the test.
(My system is PANIC-ing when asked for a realloc of 64MB. I suppose you
could also regard it as a bug that we're apparently using 64 bytes to
store each bit of information :-).
Alternatively, I suppose you could reasonab
--- parrot-current/t/pmc/resizablebooleanarray.t Sat Feb 11 12:30:37 2006
+++ parrot-andy/t/pmc/resizablebooleanarray.t Wed Feb 15 12:55:35 2006
@@ -662,7 +662,7 @@
pasm_output_is(<<'CODE', <<'OUTPUT', "direct access 2");
#new P0, .IntList
new P0, .ResizableBooleanArray
- set I10, 1100000
+ set I10, 550000
set I0, 1
lp1:
add I1, I0, 5
--
Andy Dougherty doug...@lafayette.edu
> (My system is PANIC-ing when asked for a realloc of 64MB. I suppose you
> could also regard it as a bug that we're apparently using 64 bytes to
> store each bit of information :-).
>
definitely a bug. i'll forward that to dino, who's promised to pick up
his work on the ResizableBooleanArray PMC again. in the meantime, i'll
leave this ticket open, and we'll revisit when the kinks have been
worked out of RBA.
> Alternatively, I suppose you could reasonab
>
??? hope this wasn't terribly important, it seems too have been lost
in transmission.
thanks for submitting.
~jerry
> Please resolve patch bugs after applying the patch.
In this case, I didn't apply the patch, so I didn't close it. Also, in
this case, there's more to it than just the patch -- the underlying
problem is that resizeablebooleanarray is taking 64 bytes to store 1 bit
of information. When Jerry applied that patch, he agreed that was odd and
decided to leave the ticket open pending further investigation.
--
Andy Dougherty doug...@lafayette.edu
-J
--