Re: GC: cons sweeping and cons block size

[Stefan Monnier]

> On some systems, Lisp_Object may be a tagged pointer with 29-bit (on
> 32-bit system) pointer field. Since mmap() tends to allocate memory at
> high addresses, this memory is likely to be non-addressable by such
> pointer. That is why lisp_align_malloc() currently uses
> mallopt(M_MMAP_MAX, 0) to prevent mapping the region (if underlying
> malloc() supports this). 

I haven't found the time to do it, but it would be good to get rid of this
situation and always place tags in the 3 LSB bits.


        Stefan