cerc-io/solidity
10
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

fix: rename RedundantAssignEliminator to UnusedAssignEliminator

Browse Source
This commit is contained in:
minaminao 2023-07-27 13:38:27 +09:00
parent 80d0a979ac
commit ef743aa8ac
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/internals/optimizer.rst
View File

@ -278,7 +278,7 @@ The following transformation steps are the main components:
- SSA Transform
- Common Subexpression Eliminator
- Expression Simplifier
- Redundant Assign Eliminator
- Unused Assign Eliminator
- Full Inliner
.. _optimizer-steps:
@ -315,11 +315,11 @@ Abbreviation Full name
``T`` :ref:`literal-rematerialiser`
``L`` :ref:`load-resolver`
``M`` :ref:`loop-invariant-code-motion`
``r`` :ref:`redundant-assign-eliminator`
``m`` :ref:`rematerialiser`
``V`` :ref:`SSA-reverser`
``a`` :ref:`SSA-transform`
``t`` :ref:`structural-simplifier`
``r`` :ref:`unused-assign-eliminator`
``p`` :ref:`unused-function-parameter-pruner`
``S`` :ref:`unused-store-eliminator`
``u`` :ref:`unused-pruner`
@ -631,7 +631,7 @@ the block, a new SSA variable will be created at the location where control flow
this includes the beginning of loop post/body block and the location right after
If/Switch/ForLoop/Block statement.
After this stage, the Redundant Assign Eliminator is recommended to remove the unnecessary
After this stage, the Unused Assign Eliminator is recommended to remove the unnecessary
intermediate assignments.
This stage provides best results if the Expression Splitter and the Common Subexpression Eliminator
@ -639,10 +639,10 @@ are run right before it, because then it does not generate excessive amounts of
On the other hand, the Common Subexpression Eliminator could be more efficient if run after the
SSA transform.
.. _redundant-assign-eliminator:
.. _unused-assign-eliminator:
RedundantAssignEliminator
^^^^^^^^^^^^^^^^^^^^^^^^^
UnusedAssignEliminator
^^^^^^^^^^^^^^^^^^^^^^
The SSA transform always generates an assignment of the form ``a := a_i``, even though
these might be unnecessary in many cases, like the following example:
@ -670,7 +670,7 @@ The SSA transform converts this snippet to the following:
sstore(a_3, 1)
}
The Redundant Assign Eliminator removes all the three assignments to ``a``, because
The Unused Assign Eliminator removes all the three assignments to ``a``, because
the value of ``a`` is not used and thus turn this
snippet into strict SSA form:
@ -683,7 +683,7 @@ snippet into strict SSA form:
sstore(a_3, 1)
}
Of course the intricate parts of determining whether an assignment is redundant or not
Of course the intricate parts of determining whether an assignment is unused or not
are connected to joining control flow.
The component works as follows in detail:
@ -808,7 +808,7 @@ current value if the value is an identifier.
The combination of the two rules above allow to compute a local value
numbering, which means that if two variables have the same
value, one of them will always be unused. The Unused Pruner or the
Redundant Assign Eliminator will then be able to fully eliminate such
Unused Assign Eliminator will then be able to fully eliminate such
variables.
This step is especially efficient if the expression splitter is run