693634 - Documentation for composite opcodes (e.g. ifeq) should reflect behavior of underlying operations

Status: RESOLVED WONTFIX

(Tamarin Graveyard :: Documentation, defect)

Description

[Edwin Smith]

Opcodes that are composites can be specified in terms of other opcodes and/or underlying algorithms. 

We can either duplicate the underlying descriptions or refer to them, but if we refer to them we better get it right -- details of the composite that are not relevant for the expanded opcodes should be mentioned.

Comment 1

[Edwin Smith]

For example, inclocal would be the same as getlocal, increment, setlocal, but: inclocal requires 0 operand stack slots, and is atomic; the equivalent sequence needs one stack slot and has two interior abc locations which can be targets of jumps or try-region boundaries.