https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117888
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- The question is how we should define innermost - consider - loop interchange - inlining of a function body with a loop into a loop the simplest approach might be to flag the innermost loop as written by the user in source at CFG build time (when we first record loops) and then only ever treat that as "innermost" (for heuristics) but still allow facts (a loop->inner) to override this (after interchange, inlining).
