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

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
7 years ago
3 months ago

People

(Reporter: edwsmith, Unassigned)

Tracking

unspecified
Future

Details

(Reporter)

Description

7 years ago
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.
(Reporter)

Comment 1

7 years ago
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.
Blocks: 693249
Target Milestone: --- → Future
Status: NEW → RESOLVED
Last Resolved: 3 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.