3 ms·
> its a variable length opcode encoding with a complex decoder path In practice, the performance impact of variable length encoding is largely kept in check us
by ch_123 1y ago
> its a variable length opcode encoding with a complex decoder path
In practice, the performance impact of variable length encoding is largely kept in check using predictors. The extra complexity in terms of transistors is comparatively small in a large, high-performance design.
Related reading:
https://patents.google.com/patent/US6041405A/en https://patents.google.com/patent/US6041405A/en
https://web.archive.org/web/20210709071934/https://www.anandtech.com/show/16762/an-anandtech-interview-with-jim-keller-laziest-person-at-tesla https://web.archive.org/web/20210709071934/https://www.anand...
- devnullbrain 1y agoJim Keller has a storied career in the x86 world, it isn't surprising he speaks fondly of it. Regardless: >So fixed-length instructions seem really nice when you're building little baby computers, but if you're building a really big computer, to predict or to figure out where all the instructions are, it isn't dominating the die. So it doesn't matter that much. Well, efficiency advantages are the domain of little baby computers. Better predictors give you deeper pipelines without stalls which give you higher clock speeds - higher wattages