Difference between revisions of "Instruction Set/nopf"
From Mill Computing Wiki
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{DISPLAYTITLE:nopf}} | {{DISPLAYTITLE:nopf}} | ||
− | <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|flow stream]] [[Decode|flow block]] [[Phasing|compute phase]] operation <br /> |
'''native on:''' [[Cores|all]]<br /> | '''native on:''' [[Cores|all]]<br /> | ||
</div> | </div> | ||
− | + | No operation. Flow side. | |
+ | |||
+ | Usually doesn't need to be encoded, since delays are encoded in the [[Block|encoding gap]]. | ||
+ | But for the block sizes that don't have an encoding gap, which are known for each [[Core]], the leftover entropy in the instruction header for those block sizes can encode <abbr title="No Operation">NOP</abbr>s, too. | ||
+ | |||
---- | ---- | ||
<code style="font-size:130%"><b style="color:#050">nopf</b>()</code> | <code style="font-size:130%"><b style="color:#050">nopf</b>()</code> | ||
Line 15: | Line 19: | ||
! [[Cores|Core]] || [[Slot|In Slots]]|| [[Latency|Latencies]] | ! [[Cores|Core]] || [[Slot|In Slots]]|| [[Latency|Latencies]] | ||
|- | |- | ||
− | | [[Cores/Tin/Encoding#nopf|Tin]] || f0 F0 | + | | [[Cores/Tin/Encoding#nopf|Tin]] || f0 F0 F1 || 1 |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
|- | |- | ||
− | | [[Cores/ | + | | [[Cores/Copper/Encoding#nopf|Copper]] || f0 F0 F1 || 1 |
|- | |- | ||
− | | [[Cores/ | + | | [[Cores/Silver/Encoding#nopf|Silver]] || f0 F0 F1 F2 F3 || 1 |
|- | |- | ||
− | | [[Cores/ | + | | [[Cores/Gold/Encoding#nopf|Gold]] || f0 F0 F1 || 1 |
|} | |} | ||
[[Instruction_Set|Instruction Set, alphabetical]], [[Instruction Set by Category]], [http://millcomputing.com/instructions.html?collapse=7#ops Instruction Set, sortable, filterable] | [[Instruction_Set|Instruction Set, alphabetical]], [[Instruction Set by Category]], [http://millcomputing.com/instructions.html?collapse=7#ops Instruction Set, sortable, filterable] |
Latest revision as of 13:59, 23 February 2021
No operation. Flow side.
Usually doesn't need to be encoded, since delays are encoded in the encoding gap. But for the block sizes that don't have an encoding gap, which are known for each Core, the leftover entropy in the instruction header for those block sizes can encode NOPs, too.
nopf()
operands: like Inv :
alternate encoding: skinny
Core | In Slots | Latencies |
---|---|---|
Tin | f0 F0 F1 | 1 |
Copper | f0 F0 F1 | 1 |
Silver | f0 F0 F1 F2 F3 | 1 |
Gold | f0 F0 F1 | 1 |
Instruction Set, alphabetical, Instruction Set by Category, Instruction Set, sortable, filterable