Merge pull request #4925 from wbt/patch-2

Clarify docs around reserved memory byte ranges
This commit is contained in:
chriseth 2018-09-24 16:27:21 +02:00 committed by GitHub
commit 3eb5ecdf58
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -64,7 +64,7 @@ The position of ``data[4][9].b`` is at ``keccak256(uint256(9) . keccak256(uint25
Layout in Memory Layout in Memory
**************** ****************
Solidity reserves four 32 byte slots: Solidity reserves four 32-byte slots, with specific byte ranges (inclusive of endpoints) being used as follows:
- ``0x00`` - ``0x3f`` (64 bytes): scratch space for hashing methods - ``0x00`` - ``0x3f`` (64 bytes): scratch space for hashing methods
- ``0x40`` - ``0x5f`` (32 bytes): currently allocated memory size (aka. free memory pointer) - ``0x40`` - ``0x5f`` (32 bytes): currently allocated memory size (aka. free memory pointer)