Yes, see merged PR above. It's only a workaround, not a root cause analysis + solving. But since we have similar workaround already for Win64, we can live with it for a while... In the mid term, we HAVE TO gain deeper understanding because changing the compiler is hardly a sustainable solution (and it's one shot)... So we might want to keep this issue open, or create another one with different milestones (if we start using milestones...)