Files
cpython/Objects
Tim Peters c2ce91af5f It's once again thought safe to call the pymalloc free/realloc with an
address obtained from system malloc/realloc without holding the GIL.

When the vector of arena base addresses has to grow, the old vector is
deliberately leaked.  This makes "stale" x-thread references safe.
arenas and narenas are also declared volatile, and changed in an order
that prevents a thread from picking up a value of narenas too large
for the value of arenas it sees.

Added more asserts.

Fixed an old inaccurate comment.

Added a comment explaining why it's safe to call pymalloc free/realloc
with an address obtained from system malloc/realloc even when arenas is
still NULL (this is obscure, since the ADDRESS_IN_RANGE macro
appears <wink> to index into arenas).
2002-03-30 21:36:04 +00:00
..
2000-05-02 18:34:30 +00:00
2001-08-29 23:54:21 +00:00
2002-02-01 15:34:10 +00:00
2002-03-18 20:43:51 +00:00
2002-03-22 15:33:15 +00:00
2002-03-22 15:33:15 +00:00
2002-03-22 15:33:15 +00:00
2002-03-25 11:16:18 +00:00