Totally agree software uptake is the pain point. Not even all gamer CPUs have SSE4 (https://store.steampowered.com/hwsurvey https://store.steampowered.com/hwsu

Totally agree software uptake is the pain point. Not even all gamer CPUs have SSE4 (https://store.steampowered.com/hwsurvey https://store.steampowered.com/hwsurvey), so it seems that runtime dispatch is unavoidable. Given that, if we can afford to generate code for new instruction sets and bundle it all into one slightly larger binary/library, the problem is solved, right? Highway makes it much easier to do that - no need to rewrite code for each new instruction set. As to Intel's market segmentation, we target 'clusters' of features, e.g. Haswell-like (AVX2, BMI2); Skylake (AVX-512 F/BW/DQ/VL), and Icelake (VNNI, VBMI2, VAES etc) instead of all the possible combinations.