1) The issue was reported by nobody. I just saw it reading the code.
2) It may not even exist in real world. In my test, the variable was correctly aligned on the stack.
3) It's not a severe problem on x86. If nobody from others platforms reported it, it means nobody is using it or the compiler aligned it correctly.