/* -*-c-*-
*
- * $Id: darray.c,v 1.3 1999/10/29 22:59:22 mdw Exp $
+ * $Id: darray.c,v 1.5 2000/06/17 10:37:39 mdw Exp $
*
* Dynamically growing dense arrays
*
/*----- Revision history --------------------------------------------------*
*
* $Log: darray.c,v $
+ * Revision 1.5 2000/06/17 10:37:39 mdw
+ * Add support for arena management.
+ *
+ * Revision 1.4 1999/11/06 12:40:45 mdw
+ * Minor changes to allocation strategy.
+ *
* Revision 1.3 1999/10/29 22:59:22 mdw
* New array adjustment macros for unsigned arguments.
*
#include <stdlib.h>
#include "alloc.h"
+#include "arena.h"
#include "darray.h"
/*----- Magic numbers -----------------------------------------------------*/
/* --- Maybe just shunt data around a bit --- *
*
* If the vector is large enough, then theoretically we could cope by
- * moving the objects about in their existing storage.
+ * moving the objects about in their existing storage. It's not worth
+ * bothering if there's not actually double the amount of space I need.
*/
- if (rq < b->sz + b->off) {
+ if (rq * 2 < b->sz + b->off) {
q = p - (b->off - slots) * sz;
memmove(q, p, b->len * sz);
b->sz += b->off - slots;
return (q);
}
- /* --- Reallocate the array --- *
+ /* --- Decide on a new size --- *
*
- * If the offset isn't changing, it's sensible to use @realloc@ if
- * available. Otherwise the overhead of copying all the data twice
- * probably isn't worth it.
+ * There's a minimum possible size for the array which is used if it's
+ * currently completely empty. Otherwise I choose the smallest power of
+ * two which is big enough, starting at double the current size.
*/
nsz = v ? b->sz + b->off : (DA_INITSZ >> 1);
do nsz <<= 1; while (nsz < rq);
+
+ /* --- Reallocate the block --- *
+ *
+ * If I'm not changing the base offset then it's worth using @realloc@;
+ * otherwise there'll probably be two calls to @memcpy@ to shunt the data
+ * around so it's not worth bothering.
+ */
+
if (p && slots == b->off) {
- q = xrealloc(p - b->off * sz, nsz * sz);
+ q = x_realloc(b->a, p - b->off * sz, nsz * sz);
q += slots * sz;
} else {
- q = xmalloc(nsz * sz);
+ q = x_alloc(b->a, nsz * sz);
q += slots * sz;
if (p) {
memcpy(q, p, b->len * sz);
- free(p - b->off * sz);
+ x_free(b->a, p - b->off * sz);
}
}
+
+ /* --- Fill in the other parts of the base structure --- */
+
b->off = slots;
b->sz = nsz - slots;
b->unshift = b->push = 0;
/* --- Maybe just shunt data around a bit --- *
*
* If the vector is large enough, then theoretically we could cope by
- * moving the objects about in their existing storage.
+ * moving the objects about in their existing storage. Again, if there's
+ * not actually twice the space needed, reallocate the array.
*/
- if (rq < b->sz + b->off) {
+ if (rq * 2 < b->sz + b->off) {
q = p + (b->sz - slots) * sz;
memmove(q, p, b->len * sz);
b->off += b->sz - slots;
* almost all the time -- that's the whole point of this routine!
*/
+ /* --- Decide on a new size --- *
+ *
+ * There's a minimum possible size for the array which is used if it's
+ * currently completely empty. Otherwise I choose the smallest power of
+ * two which is big enough, starting at double the current size.
+ */
+
nsz = v ? b->sz + b->off : (DA_INITSZ >> 1);
do nsz <<= 1; while (nsz < rq);
- q = xmalloc(nsz * sz);
+
+ /* --- Reallocate the block --- *
+ *
+ * The neat @realloc@ code doesn't need to be here: the offset changes
+ * almost all the time -- that's the whole point of this routine!
+ */
+
+ q = x_alloc(b->a, nsz * sz);
q += (nsz - slots) * sz;
if (p) {
memcpy(q, p, b->len * sz);
- free(p - b->off * sz);
+ x_free(b->a, p - b->off * sz);
}
+
+ /* --- Fill in the other parts of the base structure --- */
+
b->off = nsz - slots;
b->sz = slots;
b->unshift = b->push = 0;
return (p);
if (!b->len) {
- free(p - b->off * sz);
+ xfree(p - b->off * sz);
return (0);
}
- q = xmalloc(b->len * sz);
+ q = x_alloc(b->a, b->len * sz);
memcpy(q, p, b->len * sz);
- free(p - b->off * sz);
+ x_free(b->a, p - b->off * sz);
b->sz = b->len;
b->off = 0;
return (q);