https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53875
--- Comment #6 from Roger Sayle <roger at nextmovesoftware dot com> --- I believe this should be "... && optimize != 0", i.e. we want to eliminate these calls (only) when optimizing. But this seems like a reasonable fix/feature request (to identify breakpoints at -O0).
