diff options
| author | Taylan Kammer <taylan.kammer@gmail.com> | 2026-09-21 04:33:29 +0200 |
|---|---|---|
| committer | Taylan Kammer <taylan.kammer@gmail.com> | 2026-09-21 05:55:55 +0200 |
| commit | 0211733335191553bd922d933479cae01ae535c0 (patch) | |
| tree | 6fcfa9741759cb7430cdf84a2c2f2104bff38b78 /doc | |
| parent | 11f1eb1ad97797fdc287bd037842949e18960d71 (diff) | |
Meta Alloc doc fix.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/0/A-meta_alloc.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/0/A-meta_alloc.md b/doc/0/A-meta_alloc.md index 3ac005a..85c704c 100644 --- a/doc/0/A-meta_alloc.md +++ b/doc/0/A-meta_alloc.md @@ -104,14 +104,14 @@ Zisp runtime, that the operating system reports that the process is using hundreds of gigabytes of virtual memory, do not panic; it's a feature, not a bug, and completely benign. -As for the size classes: They simply go from 256 bytes to 8 MiB in -perfect powers of two; in other words, from 2^8 to 2^23. There are -certain benefits to using exact powers of two, and 256 bytes to 8M +As for the size classes: They simply go from 128 bytes to 4 MiB in +perfect powers of two; in other words, from 2^7 to 2^22. There are +certain benefits to using exact powers of two, and 128 bytes - 4 MiB seems like a reasonable range. Code using Meta Alloc must be aware that only these size classes are supported, and try to make optimal use of them. -**WARNING:** Calling `alloc()` with a size smaller than 256 or one +**WARNING:** Calling `alloc()` with a size smaller than 128 or one that is not a perfect power of two will lead to catastrophic bugs under optimized builds of Zisp. |