Re: next nightly build problem

Hi Daniel,

> Adding this because it might be related: on NetBSD I disabled
> TRIVIALMAP_MEMORY and SINGLEMAP_MEMORY because our fixed address (0x40...0)
> is not mappable there.
> 
> This was done with commit 1c61a0 [1]

While this was good to get clisp running on NetBSD at all, one can go one step
further and re-enable TRIVIALMAP_MEMORY or SINGLEMAP_MEMORY with the
appropriate address range.

For SINGLEMAP_MEMORY this was relatively easy, done through an autoconf test
("checking for highest bit number which can be included in mmaped addresses",
from m4/mmap.m4).

For TRIVIALMAP_MEMORY it is harder. For now I've specified the address range
explicitly. But it should be possible to determine it automatically,
depending on CODE_ADDRESS_RANGE, MALLOC_ADDRESS_RANGE, SHLIB_ADDRESS_RANGE,
STACK_ADDRESS_RANGE, and garcol_bit_o...

Bruno


------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel