Appendix: the VM footprint number doesn't really give us a breakdown since it includes executable and shared libs mappings. I ran the second compile again with the memory-optimized build, and this time captured a pmap.
Here you can also see the full command, confirming the compile job:
You can see the 11700K fairly closely matches the earlier VIRT figure of 11964.
Anyway, look at the [ anon ] heap area: it's like 6-something megs. That's it. That's where all the dynamic Lisp stuff is. All the predefined symbols and function bindings and whatnot, and all the objects allocated during the compile job.
libz is new; I integrated libz into TXR in just the most recent release. It happens to be number 277, so I code named it (L)Z77.
Here you can also see the full command, confirming the compile job:
You can see the 11700K fairly closely matches the earlier VIRT figure of 11964.Anyway, look at the [ anon ] heap area: it's like 6-something megs. That's it. That's where all the dynamic Lisp stuff is. All the predefined symbols and function bindings and whatnot, and all the objects allocated during the compile job.
libz is new; I integrated libz into TXR in just the most recent release. It happens to be number 277, so I code named it (L)Z77.