http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50394
--- Comment #19 from Jan Hubicka <hubicka at ucw dot cz> 2011-09-21 09:38:57 UTC --- > # silent miscompiles; LO/OOo adds -O2/1/0 where appropriate > filter-flags "-O* > > And because the effect of LTO is to fully optimize the important parts of > a program and use -Os for the rest, this could explain the crashes. GCC does not really bump up optimization levels and same heuristics is in limited degree applied w/o LTO as well. Debugging this seems quite important. Perhaps hacking -fno-strict-aliasing in addition to -flto at linktime could be first shot to get working binary?
