2 ms·
It's a bit less messy if you ignore the GPU-like Xeon Phi (Knights Landing and Knights Mill) and the failed Cannonlake that Intel definitely would prefer everyo
by wtallis 6y ago
It's a bit less messy if you ignore the GPU-like Xeon Phi (Knights Landing and Knights Mill) and the failed Cannonlake that Intel definitely would prefer everyone pretend never happened. But that still leaves you with a progression of four levels of expanding support, and the Cooper Lake mess of having BFLOAT16 but not the stuff added in Ice Lake and Tiger Lake.
If you don't cut down the support table to eliminate irrelevant niche products, it's most of the way to being a Gray code.
- dogma1138 6y agoI think Icelake and Tiger lake not having BF16 is going to be a big issue especially for machine learning applications, I can’t find what Rocket Lake supports yet but I’m guessing it’s going to be similar to Tiger Lake. There is also the big unknown of what kind of support AMD will bring to the table. I think Intel is banking on people using OneAPI more than writing AVX-512 code using intrinsics or compiler magic. At that point compatibility might be not as much of an issue if you ignore potentially drastic differences in performance.