> Does your library have to be a single compiled binary across all these variants? No no, not that. :) As Matt mentioned my work does include JIT compilers,

> Does your library have to be a single compiled binary across all these variants? No no, not that. :) As Matt mentioned my work does include JIT compilers, so I'm curious to know how many instruction variants I'd have to support. But I also want to simply test that my plain C code (ie. the interpreted, slow paths) doesn't make any platform-specific assumptions that break on some processors. > What do you mean 'supported across all (or most) ARM cores'? My intention is that anyone can compile my library out-of-the-box and have it just work, unless their CPU has a fundamental limitation that I can't support. So far the only such limitation I want to concede is that I require at least a 32-bit CPU (for one, my program's code and data will only barely fit in 64k of RAM, and wouldn't leave much space for anything else).