https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83312
--- Comment #5 from Arnd Bergmann <arnd at linaro dot org> --- (In reply to Jeffrey A. Law from comment #4) > > I think we can avoid the warning by simply clearing EDGE_EXECUTABLE on the > appropriate edge when we simplify the conditional. That won't capture > secondary effects though. We could go further and have a step that > propagates EDGE_EXECUTABLE just before we do the array bounds warnings. I'm > not sure if it's worth the effort. Thoughts? I'd say don't spend too much time on it if the effect is only improved warnings and not noticeably better optimized code. I saw only a single instance of the warning in 7500 'randconfig' kernel builds with a recent gcc snapshot, and never before with earlier versions.
