Locality problems caused by size based allocation?

[Fergus Henderson]

On 17-Dec-2002, Daniel Berlin <dberlin@dberlin.org> wrote:
> 
> On Tue, 17 Dec 2002, Jeff Sturm wrote:
> > Pointer misidentification is certainly common
> > with a conversative collector, but 50% lossage is quite rare.
> 
> Not in gcc.
>
> > And if
> > that were happening you'd see plenty of blacklisted pointers (unless all
> > messages are suppressed, as with -DSILENT).
> 
> You do.
> 100's of k worth.

In that case, it may help to provide the collector with a little more
type information, e.g. using GC_malloc_atomic() rather than GC_malloc()
where appropriate (e.g. for things like strings and floating point numbers).
Often a small number of allocation sites are responsible for the allocations
which result in most of the words which are misidentified as pointers.

-- 
Fergus Henderson <fjh@cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.