cerc-io/solidity
16
0
Fork 0
mirror of https://github.com/ethereum/solidity synced 2023-10-03 13:03:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #12322 from tzann/patch-1

Browse Source 
Fix ExpressionSplitter example
This commit is contained in:
chriseth 2021-12-01 15:44:57 +01:00 committed by GitHub
commit d2585fd91d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/internals/optimizer.rst
View File

@ -521,7 +521,7 @@ ExpressionSplitter
The expression splitter turns expressions like ``add(mload(0x123), mul(mload(0x456), 0x20))``
into a sequence of declarations of unique variables that are assigned sub-expressions
of that expression so that each function call has only variables or literals
of that expression so that each function call has only variables
as arguments.
The above would be transformed into
@ -529,10 +529,13 @@ The above would be transformed into
.. code-block:: yul
{
let _1 := mload(0x123)
let _2 := mul(_1, 0x20)
let _3 := mload(0x456)
let z := add(_3, _2)
let _1 = 0x20
let _2 = 0x456
let _3 = mload(_2)
let _4 = mul(_3, _1)
let _5 = 0x123
let _6 = mload(_5)
let z = add(_6, _4)
}
Note that this transformation does not change the order of opcodes or function calls.
@ -543,7 +546,7 @@ this "outlining" of the inner expressions in all cases. We can sidestep this lim
The final program should be in a form such that (with the exception of loop conditions)
function calls cannot appear nested inside expressions
and all function call arguments have to be literals or variables.
and all function call arguments have to be variables.
The benefits of this form are that it is much easier to re-order the sequence of opcodes
and it is also easier to perform function call inlining. Furthermore, it is simpler