![](https://secure.gravatar.com/avatar/d8110a8a8a97be0803549ea5ee2e638b.jpg?s=120&d=mm&r=g)
7 Oct
2007
7 Oct
'07
11:36 p.m.
2007/10/6, George N. White III
Why not file a bug report against gcc and wait a while to see if clarity emerges? It may be a plain bug in gcc so the code can be left as is and the flags changed until most people have the fixed version, or a case where the optimizer sometimes makes bad choices and you are better off changing the code to circumvent the issue.
I did better: I asked the gcc experts for help -- and got it. See http://gcc.gnu.org/ml/gcc-help/2007-10/msg00076.html and the followups. Best Martin