On 6/16/23 06:37, Jordy Zomer wrote: > array_index_nospec() should only be used if the upper boundary is a built > time constant. Otherwise the boundary could be speculated on as well. > While it might be more difficult to control two loads, it doesn't rule > out the problem. Adding this to the documentation so people won't mis-use > it instead of barrier_nospec(). Then shouldn't we be using __builtin_constant_p() to enforce this?
