Difference between revisions of "Instruction Set/exuArgs"
From Mill Computing Wiki
m (Protected "Instruction Set/exuArgs": generated ([Edit=<protect-level-bot>] (indefinite) [Move=<protect-level-bot>] (indefinite))) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:exuArgs}} | {{DISPLAYTITLE:exuArgs}} | ||
| − | <div style="font-size:80%;line-height:90%;margin-bottom:2em">[[Speculation| | + | <div style="font-size:80%;line-height:90%;margin-bottom:2em">[[Speculation|speculable]] [[Encoding|exu stream]] [[Decode|exu block]] [[Phasing|compute phase]] operation <br /> |
'''native on:''' [[Cores|all]]<br /> | '''native on:''' [[Cores|all]]<br /> | ||
</div> | </div> | ||
Revision as of 09:32, 9 February 2015
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 |
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
