Hello, On Mon, 17 Nov 2025, Richard Biener wrote:
> I suppose all passes that eventually care about profile (jump threading > does, in its cost metrics, via maybe_hot/optimize_edge_for_speed, > falling back to global defaults) would benefit from some kind of > reasonable local profile. > > Now, I can simply move early LIM later, right after pass_profile > for example. I'd expect if-to-switch / switch-convert disrupting > the profile. > > Any ideas here? As a full LIM follows later anyway there's always the option to make the early one not depend on a proper profile, but rather just _never_ move expense operations out of their containing loops. That will disable it on some loops, but that's also the case without any early LIM at all, after all :) Ciao, Michael.
