This is Operating System-dependent:
On Windows, LispWorks is mapped at
#x20000000
, and in principle can grow up to some distance below
#x80000000
(almost 1.5GB). In practice there is always the possibility that some DLL will be mapped in this region. On startup, LispWorks reserves 0.5GB above its location, so that much is guaranteed.
On Linux, 32-bit LispWorks is mapped at
#x20000000
, but you can map it elsewhere as described under --relocate-image address. In principle LispWorks can grow up to some distance below
#xBF000000
(almost 2.5GB), though this depends on the OS kernel allowing this size. In practice, the shared libraries are always mapped somewhere in this space. LispWorks now has a mechanism to automatically skip over the libraries, and hence may approach 2.4GB. Again this is kernel-dependent.
On Mac OS X, 32-bit LispWorks is mapped at
#x20000000
and can grow around 2.7GB. On the Intel architecture, you can map it elsewhere as described under --relocate-image address provided that the address space is not used by something else.
On FreeBSD, LispWorks is mapped at
#x30000000
, but you can map it elsewhere as described under --relocate-image address. In principle LispWorks can grow up to some distance below
#xC0000000
(almost 2.25GB), though this depends on the OS kernel allowing this size and how many threads you have running.
On Solaris, LispWorks is mapped at
#x10000000
. In principle it can grow to almost
#x80000000
(the libraries are at higher addresses).
On HP-UX, LispWorks is mapped at
#x50000000
, because it cannot use the first quadrant. The libraries are also mapped at the same quadrant, at around
#x7a000000
, so the total size can be a little more than 0.5GB.