On Jan 14, 2008 3:54 AM, Pavel Cahyna <[EMAIL PROTECTED]> wrote: > > I'm seeing mysterious testsuite failures when the entire binary is > > compiled with -O2, and fewer, different mysterious testsuite failures > > when the entire binary is compiled with -O1. See > > I had to disable optimizations; -O1 did not work, either.
Just to be clear: you get *reproducible* testsuite failures when the entire binary is compiled with -O1, and none when it is compiled with -O0? If so, that is either a compiler bug indeed, or a place where gcc has gotten cleverer with its optimizations and broken an improper assumption in the source code. Either way, the next step, if you're up for it, would be to find out which object file has the bad machine code in it (start from an -O0 build, and one at a time, swap out .o files for ones compiled at -O1, relink and retest; don't neglect lib3rdparty.a). zw _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
