Found in GCC 6's changelog (http://gcc.gnu.org/gcc-6/changes.html):
> Value range propagation now assumes that the this pointer of C++ member > functions is non-null. This eliminates common null pointer checks but also > breaks some non-conforming code-bases (such as Qt-5, Chromium, KDevelop). > As a temporary work-around -fno-delete-null-pointer-checks can be used. > Wrong code can be identified by using -fsanitize=undefined. Are we free of such mistakes? Or do we need to enable -fno-delete-null- pointer-checks? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
