SBCL Internals : Memory Map

SBCL Internals
The pages on this CLiki-driven site can be edited by anybody at any time. No warranty of any kind can therefore be made; any implied warranties of merchantability or fitness for a particular purpose are expressly disclaimed

[ Home ]

[ Recent Changes ]

[ About CLiki ]

[ Text Formatting ]

SBCL depends at a fairly fundamental level on being able to map memory for its various workspaces at fixed addresses. The addresses for a given architecture can be found in src/compiler/$SBCL_ARCH/parms.lisp - look for a bunch of constants with names of the form foo-space-{start,end} and hex values

These tend to be selected empirically and are supposed to do things like not overlap with program text, the C stack/heap, or shared libraries.

Read-only Space?
Static Space?
Dynamic Space? or spaces. Ports which use the Stop and Copy GC need two dynamic spaces so that GC can copy from one to the other
Control Stack
Binding Stack?

This page is linked from: Once And Only Once

CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively