https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69234
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Markus Trippelsdorf from comment #5) > BTW, Honza promised to implement a -fnull-this-pointer switch for this issue, > because Firefox, Kdevelop, QT5, etc. are also affected. Sounds like so many folks depends on this undefined behavior. It is sad it was not until GCC 6 people are finding this undefined behavior. I rather have people fix their code rather than changing GCC. Since -fsantize=undefined will find it. There is no reason to have another flag to disable the optimization.
