4 ms·
My interpretation of this (based on what the article says) is that you are providing an opcode->[instructions or microcode?] mechanism? Which seems unlikely to
by olliej 7y ago
My interpretation of this (based on what the article says) is that you are providing an opcode->[instructions or microcode?] mechanism?
Which seems unlikely to be correct, because they already have licenses that allow new instructions/features.
So is it actually "this instruction should be turned into these signals to these ports"?
(I'll try to read the white paper once I'm not on a phone)
- olliej 7y agoOk, so based on https://www.arm.com/why-arm/technologies/custom-instructions https://www.arm.com/why-arm/technologies/custom-instructions It sounds like this is that you get to specify custom RTL for a given opcode, you are still restricted to whatever functionality is in the standard ALU. The problem I'm having with the public docs is that they all seem to say "you can replace this [hand coded assembly example] with [a custom opcode]", but don't give an example of the actual implementation of the opcode. That would at least show some sense of what is possible.