[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GC: cons sweeping and cons block size
From: |
David Kastrup |
Subject: |
Re: GC: cons sweeping and cons block size |
Date: |
Thu, 05 Jul 2007 16:42:21 +0200 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/23.0.51 (gnu/linux) |
Stefan Monnier <address@hidden> writes:
>> 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.
Would that impact the severity of YAILM (or what the integer/lisp
mixups were called) occurences?
--
David Kastrup