You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...
tag_7:
/* "condition.sol":270:277 uint256 */
0x00
/* "condition.sol":297:298 b */
dup2
/* "condition.sol":293:294 a */
dup4
/* "condition.sol":293:298 a > b */
gt
/* "condition.sol":293:309 a > b || a > 100 */
dup1
tag_11
jumpi
pop
/* "condition.sol":306:309 100 */
0x64
/* "condition.sol":302:303 a */
dup4
/* "condition.sol":302:309 a > 100 */
gt
/* "condition.sol":293:309 a > b || a > 100 */
tag_11:
/* "condition.sol":289:348 if (a > b || a > 100) {... */
iszero
tag_12
jumpi
/* "condition.sol":336:337 b */
dup2
/* "condition.sol":332:333 a */
dup4
/* "condition.sol":332:337 a - b */
…
In tag_7, there is a 'POP' just after 'JUMPI', which means the original value of the DUP is not used. Although this value is used in the other branch(tag_11), this can also be optimized.
Optimization
Specifically, moving tag_11 after iszero tag_12 jumpi would achieve this optimization. The resulting assembly code is as follows:
...
tag_7:
/* "condition.sol":270:277 uint256 */
0x00
/* "condition.sol":297:298 b */
dup2
/* "condition.sol":293:294 a */
dup4
/* "condition.sol":293:298 a > b */
gt
/* "condition.sol":293:309 a > b || a > 100 */
tag_11
jumpi
/* "condition.sol":306:309 100 */
0x64
/* "condition.sol":302:303 a */
dup4
/* "condition.sol":302:309 a > 100 */
gt
/* "condition.sol":293:309 a > b || a > 100 */
iszero
tag_12
jumpi
tag_11:
/* "condition.sol":336:337 b */
dup2
/* "condition.sol":332:333 a */
dup4
/* "condition.sol":332:337 a - b */
…
In this way, for a>b, it will execute PUSH1 DUP2 DUP4 GT PUSH2 JUMPI JUMPDEST DUP2 DUP4 instead of PUSH1 DUP2 DUP4 GT DUP1 PUSH2 JUMPI JUMPDEST ISZERO PUSH2 JUMPI DUP2 DUP4 . For a<=b and a>100, it will execute PUSH1 DUP2 DUP4 GT PUSH2 JUMPI PUSH1 DUP4 GT ISZERO PUSH2 JUMPI JUMPDEST DUP2 DUP4 instead of PUSH1 DUP2 DUP4 GT DUP1 PUSH2 JUMPI POP PUSH1 DUP4 GT JUMPDEST ISZERO PUSH2 JUMPI DUP2 DUP4 .
Is it possible to move the Instruction::ISZERO and conditionalJump in this function to the front of the endLabel in the function appendAndOrOperatorCode?
The text was updated successfully, but these errors were encountered:
Description
The above function will generate the following opcode.
The corresponding assembly code is:
In tag_7, there is a 'POP' just after 'JUMPI', which means the original value of the DUP is not used. Although this value is used in the other branch(tag_11), this can also be optimized.
Optimization
Specifically, moving tag_11 after
iszero tag_12 jumpi
would achieve this optimization. The resulting assembly code is as follows:In this way, for a>b, it will execute
PUSH1 DUP2 DUP4 GT PUSH2 JUMPI JUMPDEST DUP2 DUP4
instead ofPUSH1 DUP2 DUP4 GT DUP1 PUSH2 JUMPI JUMPDEST ISZERO PUSH2 JUMPI DUP2 DUP4
. For a<=b and a>100, it will executePUSH1 DUP2 DUP4 GT PUSH2 JUMPI PUSH1 DUP4 GT ISZERO PUSH2 JUMPI JUMPDEST DUP2 DUP4
instead ofPUSH1 DUP2 DUP4 GT DUP1 PUSH2 JUMPI POP PUSH1 DUP4 GT JUMPDEST ISZERO PUSH2 JUMPI DUP2 DUP4
.solidity/libsolidity/codegen/ExpressionCompiler.cpp
Lines 2367 to 2380 in b849b32
In this function, the endLabel is tag_11 in this example.
solidity/libsolidity/codegen/ContractCompiler.cpp
Lines 1153 to 1172 in b849b32
Is it possible to move the Instruction::ISZERO and conditionalJump in this function to the front of the endLabel in the function appendAndOrOperatorCode?
The text was updated successfully, but these errors were encountered: