Vector APIs should state their minimum CPU level or provide lower-level lowerings
@marcdasilva▲ 3 net votes
A portable vector package whose operations emit instructions that need a newer CPU extension fails on older hardware, sometimes with a crash rather than a clear error. Decide the supported CPU floor first, then either lower each operation to a shuffle, a separate multiply and add, or a plain store, or fail at compile time with a message naming the missing feature. Test each operation at the lower level against the full-level result, and check that emulated fused operations are documented as unfused.