Masked access behaves differently when compiling with -mavx2 about enoki

[gergol]

It turns out that it works with using M = mask_t<Array<bool, 8>>;. Maybe I do not fully understand the proper use of masks (unfortunately I have no experience with SIMD yet), so if this is not a bug, it could be helpful to add a short section in the docs how to properly create masks manually.

[wjakob]

Hi Gergol,

the problem is the way in which you manually create a mask, which is basically an implementation detail of the underlying implementation. A mask is a 1-bit value per lane on some targets (AVX512 K mask registers), a 1 byte boolean on other targets, and a full 32 bit value on AVX/AVX2. So for this specific target, you would have to use 0xffffffff instead of 1. Arguably the constructor for masks could be implemented in a nicer way so that it unifies these cases. Then, on the other hand, creating a mask by hand in this way is probably a fairly obscure use case.

Best,
Wenzel

[wjakob]

(Normally masks are the result of some actual computation, in which case they will naturally have the right representation.)

[gergol]

Hi Wenzel!

Thanks for the quick reply! The confusing thing is that all masks look identical (containing 1s and 0s) when printed, even if they show different behaviour. Looking at them with the debugger revealed what you wrote in your first post. My use case was to try to write into the odd/even values of a packet to calculate the magnitudes of the interleaved complex STFT result from my other issue.