https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103724
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org,
| |msebor at gcc dot gnu.org
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
One thing we could do is annotate struct loop * with the (high level)
optimizations we've applied so that when we emit this warning we could say
note: this loop is the copy generated by loop unswitching where b == 0
or so. Or maybe at least show
note: this loop was unswitched
the optimization-report/opt-info machinery might have a way to "queue"
such stuff. For sure not in a directly usable way. Likewise jump threadings
could record BB origins as "part of a threaded path covering conditions at
loc1, loc2" or so.
