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
{{ message }}
This repository was archived by the owner on Nov 3, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: document/core/syntax/instructions.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,7 +138,7 @@ For each type, several subcategories can be distinguished:
138
138
* *Comparisons*: consume two operands of the respective type and produce a Boolean integer result.
139
139
140
140
* *Conversions*: consume a value of one type and produce a result of another
141
-
(the source type of the conversion is the one after the ":math:`\K{/}`").
141
+
(the source type of the conversion is the one after the ":math:`\K{\_}`").
142
142
143
143
Some integer instructions come in two flavors,
144
144
where a signedness annotation |sx| distinguishes whether the operands are to be :ref:`interpreted <aux-signed>` as :ref:`unsigned <syntax-uint>` or :ref:`signed <syntax-sint>` integers.
@@ -377,7 +377,7 @@ In case of |LOOP| it is a *backward jump* to the beginning of the loop.
377
377
378
378
.. note::
379
379
This enforces *structured control flow*.
380
-
Intuitively, a branch targeting a |BLOCK| or |IF| behaves like a :math:`\K{break}` statement,
380
+
Intuitively, a branch targeting a |BLOCK| or |IF| behaves like a :math:`\K{break}` statement in most C-like languages,
381
381
while a branch targeting a |LOOP| behaves like a :math:`\K{continue}` statement.
0 commit comments