https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109985
Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Hmm, this is slipperly. So novops tells gcc that the function has on memory side effects and in turn we optimize out the call? I think we need to handle novops as having side-effects.