cerc-io/solidity
11
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 #2384 from ethereum/parseFunctionalInstructions

Browse Source 
Enforce function arguments when parsing functional instructions.
This commit is contained in:
chriseth
2017-06-14 18:35:16 +02:00
committed by GitHub
parent d693822a6f 98139ead42
commit fd5bf16101
4 changed files with 29 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/assembly.rst
+4 -2
View File
@@ -318,8 +318,10 @@ would be written as follows
mstore(0x80, add(mload(0x80), 3))
Functional style and instructional style can be mixed, but any opcode inside a
functional style expression has to return exactly one stack slot (most of the opcodes do).
Functional style expressions cannot use instructional style internally, i.e.
``1 2 mstore(0x80, add)`` is not valid assembly, it has to be written as
``mstore(0x80, add(2, 1))``. For opcodes that do not take arguments, the
parentheses can be omitted.
Note that the order of arguments is reversed in functional-style as opposed to the instruction-style
way. If you use functional-style, the first argument will end up on the stack top.