Predication (computer architecture): Difference between revisions

Content deleted Content added
Put simply: not all machines with predicated instructions have a condition code register - MIPS added conditional moves in MIPS IV, but it has no condition code register, so the move is done only if another register specified in the instruction is zero (MOVZ) or non-zero (MOVN).
Those are all branch instructions; no need to list them all individually. (Yes, a subroutine call or return is a branch, and a "branch table" is something that contains targets of branches.) This makes it a bit clearer that predication isn't implemented with branches, it's an *alternative* to branches. (And, yes, the next sentence needs to be fixed to make it clearer that it replaces branches.)
Line 1:
{{More citations needed|date=March 2014}}
{{Distinguish|Branch prediction}}
In [[computer science]], '''predication''' is an [[computer architecture|architectural]] feature that provides an alternative to conditional transfer of [[control flow|control]], as implemented by conditional [[instructionbranch (computer science)|machine instructionsbranch]] such as conditional [[branchinstruction (computer science)|branch]],machine conditional [[subroutine|call]], conditional [[return statement|return]], and [[branch tableinstructions]]s. Predication works by executing instructions from both paths of the branch and only permitting those instructions from the taken path to modify architectural state.<ref name="rvinyard">{{cite web
|url= https://www.cs.nmsu.edu/~rvinyard/itanium/predication.htm
|title= Predication