http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53728
--- Comment #10 from Uros Bizjak <ubizjak at gmail dot com> 2013-04-04 06:41:39 UTC --- (In reply to comment #9) > Any chance of looking at this before the 4.6 branch closes? If not we can > work > around it locally. I have analysed the failure, and it is in fact a compare-debug failure, where presence of debug instructions changes the compilation slightly. The result is *not* wrong code, but a different (and possibly slightly non-optimal) code. However, as found in the description, the problem was indeed fixed by the big update of a register allocator functionality [1], and it is nearly impossible to find a small and self-contained change that fixed this particular problem. The referred change that was identified as a cause to this problem has nothing to do with register allocator, it just exposes the problem. I propose to close the bug as WONTFIX for 4.6 branch. [1] http://gcc.gnu.org/viewcvs/gcc?view=revision&revision=171649
