https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53875
--- Comment #6 from Roger Sayle ---
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).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53875
Andrew Pinski changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53875
--- Comment #4 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #3)
> The code which introduced this was
> g:8c6a82695b85f8ed74cdc67f2cf74c5a62d0d91d .
https://gcc.gnu.org/pipermail/gcc-patches/2003-May/104797.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53875
Andrew Pinski changed:
What|Removed |Added
Known to work||3.3.3
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53875
Andrew Pinski changed:
What|Removed |Added
Component|c++ |middle-end
--- Comment #2 from Andrew
