Difference between revisions of "Instruction Set/exuArgs"

From Mill Computing Wiki
Jump to: navigation, search
m (Protected "Instruction Set/exuArgs": generated ([Edit=<protect-level-bot>] (indefinite) [Move=<protect-level-bot>] (indefinite)))
(No difference)

Revision as of 01:35, 3 January 2015

realizing  exu stream  exu block  compute phase   operation  

native on: all

Additional arguments for Ganged operations.

All data paths for the operands of compute operations are optimized for 2 operands. Yet some operations need more. For those operations, like fmaf or inject, a primary opcode in one Slot and the `exuArgs` opcode in the next together form the full operation with all operands.

This is possible because neighboring Slots and their Pipelines can pass data between each other in a side path without needing a full interconnecting data path.


exuArgs(op arg)

operands: like Inv :


Core In Slots Latencies
Tin E0 E1 0
Copper E0 E1 0
Silver E0 E1 E2 E3 0
Gold E0 E1 E2 E3 E4 E5 E6 E7 0
Decimal8 E0 E1 E2 E3 0
Decimal16 E0 E1 E2 E3 0

exuArgs(op arg0, op arg1)

operands: like Inv :


Core In Slots Latencies
Tin E0 E1 0
Copper E0 E1 0
Silver E0 E1 E2 E3 0
Gold E0 E1 E2 E3 E4 E5 E6 E7 0
Decimal8 E0 E1 E2 E3 0
Decimal16 E0 E1 E2 E3 0


Instruction Set, alphabetical, Instruction Set by Category, Instruction Set, sortable, filterable