------- Comment #27 from fejj at novell dot com 2010-01-30 23:34 ------- Steven: okay, thanks for the explanation.
My concern is that if I hit a similar case down the road and someone builds with different optimization flags than I do, that I'd never figure out the problem. It was pure luck that I tracked it down to strict aliasing in this case because when I found that -O0 and -O2 produced different code, my first instinct was to google "gcc 4.4 broken" (or some such) and it turned up pages and pages of links to people with similar (although not exactly identical) problems on various mailing-lists and decided to try -fno-strict-aliasing and it worked. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42907
