Skip to content

Commit b1315fa

Browse files
author
Timon Karnezos
committed
Updated STORAGE.markdown to reflect minimum log2m.
1 parent f1845c7 commit b1315fa

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

STORAGE.markdown

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Schema Version
7272
* the highest 3 bits are used to encode the integer value `registerWidth - 1`, and
7373
* the remaining 5 bits encode the integer value `log2(numberOfRegisters)`.
7474

75-
`registerWidth` may take values from 1 to 8, inclusive, and `log2(numberOfRegisters)` may take on 1 to 31, inclusive.
75+
`registerWidth` may take values from 1 to 8, inclusive, and `log2(numberOfRegisters)` may take on 4 to 31, inclusive.
7676

7777
For example:
7878

@@ -164,4 +164,4 @@ Schema Version
164164
* if `sparseEnabled = 0` and `explicitCutoff = 63`, then the criteria for promotion is implementation-dependent, as this value of `explicitCutoff` indicates an 'auto' promotion mode. Since `sparseEnabled = 0` the set can only be promoted to a `FULL` set.
165165
* if `sparseEnabled = 1` and `explicitCutoff = 63`, then the promotion is implementation-dependent, as this value of `explicitCutoff` indicates an 'auto' promotion mode. Since `sparseEnabled = 1` the set can only be promoted to a `SPARSE` set.
166166

167-
* When inserting an element into a `SPARSE` set, if that element would cause the storage size of the `SPARSE` set to be greater than that of a `FULL` set, then it is promoted to a `FULL` set.
167+
* When inserting an element into a `SPARSE` set, if that element would cause the storage size of the `SPARSE` set to be greater than that of a `FULL` set, then it is promoted to a `FULL` set.

0 commit comments

Comments
 (0)