2 ms·
A low power core that’s 9-way for decode and 8-way for issue? Did we solve some basic thing that made very wide architectures more feasible? Or addressed the di
by rayiner 2y ago
A low power core that’s 9-way for decode and 8-way for issue? Did we solve some basic thing that made very wide architectures more feasible? Or addressed the diminishing returns to wider issue? It took Intel about 10 years to go from 3-way issue in the P6 to 4-way in Conroe. But in the last decade we’re up to 8-way in an Atom CPU!
- deleted 2y ago[deleted]
- whizzter 2y agoWell back in the P6 to Conroe timespan we had that detour for more Ghz with P4 that turned out badly where probably assumed wider issue wouldn't be an issue when you increased the clockrate. Also back in those days 32bit x86 with it's anemic 8 GP registers (and stack-based-fpu) it was hard to avoid any dependencies w/o trying to calculate memory positions, nowadays we have 64bit x86 with 16 GP registers and separated FPU XMM registers (compilers can leave much more in memory and registers are probably far easier to do dependency resolution on). Oh and a theory could be that JS,Java,C#,Rust,etc code with lots of non-taken safety barriers(out of bounds, type-tests,etc) has probably been analyzed and been found to be a prime candidate for parallell issue.
- ColonelPhantom 2y agoI'm not entirely sure about the backend, but for the frontend Intel has come up with a 'split decoder'. Essentially, Skymont will have 3x 3-wide decoders working in parallel on different parts of the instruction stream. I have no idea how they find points to perform load-balancing between these clusters (outside of taken branches), but the 2x3-wide setup in Gracemont seems to work like a charm after some improvements over Tremont which debuted the split decoder scheme. > This scheme appeared with Tremont, where it could only switch decoders at taken branch boundarie and Gracemont improves load balancing between the two decode clusters by automatically switching, instead of relying on taken branches. That helps performance in very long unrolled loops, which could get stuck on one decode cluster on Tremont. When we tested with longer loop lengths, we didn’t see any drop off in Gracemont’s instruction throughput: - https://chipsandcheese.com/2021/12/21/gracemont-revenge-of-the-atom-cores/ https://chipsandcheese.com/2021/12/21/gracemont-revenge-of-t...