Last Comment Bug 693634 - Documentation for composite opcodes (e.g. ifeq) should reflect behavior of underlying operations
: Documentation for composite opcodes (e.g. ifeq) should reflect behavior of un...
Status: NEW
Product: Tamarin
Classification: Components
Component: Documentation (show other bugs)
: unspecified
: All All
: -- normal (vote)
: Future
Assigned To: Nobody; OK to take it and work on it
Depends on:
Blocks: 693249
  Show dependency treegraph
Reported: 2011-10-11 08:45 PDT by Edwin Smith
Modified: 2011-10-11 08:50 PDT (History)
0 users
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description Edwin Smith 2011-10-11 08:45:04 PDT
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 2011-10-11 08:50:19 PDT
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.

Note You need to log in before you can comment on or make changes to this bug.