This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tree-optimization/69989] [6 Regression] ICE on x86_64-linux-gnu at -O3 in both 32-bit and 64-bit modes (in verify_loop_structure, at cfgloop.c:1639)


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69989

--- Comment #11 from Jeffrey A. Law <law at redhat dot com> ---
The last proposal (clear LOOPS_NEED_FIXUP) is a possibility.  I can poke at
that a bit, but I really wonder if it'd be better for gcc-7 and for gcc-6 if we
should just use localized fixups rather than trying to detect in the CFG
manipulation bits.

I think the big question here is  how do we want the CFG manipulations to
interact with loop structures in the long term.  

And it's not just edge removal that can turn an irreducible loop into a natural
loop -- that can happen with block/edge duplication as well.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]