>The problem is that AVX-512 isn’t a singular instruction set. Sure, but the bigger and (imo) the actual problem is that avx-512 was never popular enough(until

>The problem is that AVX-512 isn’t a singular instruction set. Sure, but the bigger and (imo) the actual problem is that avx-512 was never popular enough(until now i guess), adopted in the eyes of the consumers buying hardware. Intel pioneered it somewhat prematurely: just like their octane they tried to make it work (so fast) they forgot people actually need some time to adopt.[Key point: adoption based on needs, which was lower because virtually no dev adopted avx-512 for the masses to 'need' it] In this case avx-512 is a thing that can benefit way more people than the "octane" audience(I'm giving this example because octane died somewhat similarly to how intel abandoned avx-512). Right now AMD ironically steers the avx-512 ship: because what matters most is if many people can get their hands on it: that drives software adoption and importance to devs. Intel should humbly come back to avx-512 now that AMD seems to (hopefully) steadily but surely put avx-512 in all their chips.