Wheel on PyPi doesn't work on systems without AVX512 about bitshuffle HOT 3 CLOSED

@sk1p sorry for the delay. Just started having the same issue myself and so I checked back here. I'll try and tweak the CI builds to make sure this doesn't happen.

from bitshuffle.

I'm trying to come up with a good solution here. I think what's going on is that the optimiser is turning standard code into AVX instructions. Initially I'd thought just using an earlier -march setting would be what was required, but I now worry that will mean that the code explicitly calling AVX intrinsics won't be built in. I think that a combination of a late -march but an earlier -mtune might do what we want, i.e. the generic code is lightly optimised to non AVX512 instructions, but the code using AVX512 intrinsics still builds, but I need to test this.

from bitshuffle.

Hm, I didn't look into the details, but one option would be to build multiple versions into one generic wheel - for example, function multi-versioning could be used. That would possibly allow to make it still work on hardware without AVX512, yet take advantage of recent vector instruction sets on supporting hardware.

from bitshuffle.