> You can tell the compiler that this is safe either by loading both values before the ifAs I mentioned in my other email, this is true (and I believe the best work around). My two objections are that it's now two more lines of code. The other is that taking both paths is no longer an available optimization, but instead part of the code. So, even when it doesn't vectorize, there's now an additional load that happens for all compilations.