http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501
--- Comment #64 from Chen Gang <gang.chen at asianux dot com> --- (In reply to Manuel López-Ibáñez) > Firstly, thank you very much for keeping tracing this bug almost 10 years, and provided your suggestions as much as possible. What you have done is valuable to developers (at least to me); at least the developers can easily and quickly know about this gcc common issue in time, and they will notice about it and think another ways to process this issue in their own projects (e.g. firstly compile with -O0 to see warnings). And sorry for I am not quite familiar with gcc compilier implementation, so at least now, I can not fix this issue, although of cause this issue really can be fixed (just as what you said). Thanks again.