Difference between revisions of "Instruction Set/nope"
From Mill Computing Wiki
| Line 25: | Line 25: | ||
| [[Cores/Silver/Encoding#nope|Silver]] || e0 E0 || 1 | | [[Cores/Silver/Encoding#nope|Silver]] || e0 E0 || 1 | ||
|- | |- | ||
| − | | [[Cores/Gold/Encoding#nope|Gold | + | | [[Cores/Gold/Encoding#nope|Gold]] || e0 E0 || 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 14:05, 23 February 2021
No operation. Exu 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.
nope()
operands: like NoArgs :[x]
alternate encoding: skinny
| Core | In Slots | Latencies |
|---|---|---|
| Tin | e0 E0 | 1 |
| Copper | e0 E0 | 1 |
| Silver | e0 E0 | 1 |
| Gold | e0 E0 | 1 |
Instruction Set, alphabetical, Instruction Set by Category, Instruction Set, sortable, filterable
