This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/71466] [7 Regression] wrong code at -O3 on x86_64-linux-gnu
- From: "law at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 11 Jun 2016 03:26:23 +0000
- Subject: [Bug tree-optimization/71466] [7 Regression] wrong code at -O3 on x86_64-linux-gnu
- Auto-submitted: auto-generated
- References: <bug-71466-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71466
--- Comment #8 from Jeffrey A. Law <law at redhat dot com> ---
Jan,
It's a nice theory, but if that were the case I'd expect we'd be having these
problems before pulling the backwards threading bits into their own pass. I'm
pretty sure the iterations data isn't even initialized when the first couple
instances of the backwards threader are run.
What is interesting about these tests is we're threading the backedge into a
deeper point in the loop. That deeper point happens to also be the header of a
nested loop. So there's some chance we've mucked up other aspects of the loop
structures in an unexpected way.
The three BZs are almost certainly the same issue though from looking at the
CFGs and what jumps are being threaded.