https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122058
--- Comment #44 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Richard Biener from comment #43) > (In reply to Jan Hubicka from comment #41) > > + PROF_64 = [obj_type_ref] OBJ_TYPE_REF(_12;(struct > > ModifierStore)prephitmp_74->2B); > > + if (PROF_64 == > > _ZThn8_NK3icu6number4impl15LongNameHandler11getModifierENS1_6SignumENS_14Stan > > dardPlural4FormE.localalias) > > + goto <bb 8>; [24.00%] > > + else > > + goto <bb 9>; [76.00%] > > + > > + <bb 8> [local count: 229067787]: > > > > .... > > > > + goto <bb 13>; [100.00%] > > + > > + <bb 9> [local count: 725381317]: > > + PROF_68 = [obj_type_ref] OBJ_TYPE_REF(_12;(struct > > ModifierStore)prephitmp_74->2B); > > > > We definitely miss optimization here; PROF_68 is the same as PROF_64. I > > suppose FRE is confused by OBJ_TYPE_REF? > > FRE doesn't handle OBJ_TYPE_REF in any specific way. It's semantics > were never very clear to me and we seem to rely on its presence and thus > lowering it like RTL expansion does on its own isn't wanted. OBJ_TYPE_REF > is GIMPLE_SINGLE_RHS and VN simply drops OBJ_TYPE_REF to varying. That is, we can value-number OBJ_TYPE_REF as if it were just its OBJ_TYPE_REF_EXPR, but I'm not sure that would be a good thing.
