[kaffe] memory allocation

[Patrick Tullmann]

> However, this is memory allocation that is used during the
> verification of a single method and is then freed after, so it
> doesn't make any sense to allocate it with the overhead of garbage
> collection.

If its not a dynamically sized object, you might put it on the stack.

Alternatively, look at the "fixed" allocation type (GC_ALLOC_FIXED).
Probably the right thing to do is use a new GC type like
GC_ALLOC_JITTEMP did (see gcFuncs.c:initCollector).  Fixed types are
manually managed, but are separated for statistical reasons.

-Pat

----- ----- ---- ---  ---  --   -    -      -         -               -
Pat Tullmann                                       tullmann@cs.utah.edu
     To understand recursion one must first understand recursion.