Fwd: [Development] Are we free of code that checks this isn't null?

[Kevin Funk]

Are *we* free of it?

Simply using this under Clang should tell us about all occurrences:
  -Werror=undefined-bool-conversion

/me checks

Cheers,
Kevin

----------  Forwarded Message  ----------

Subject: [Development] Are we free of code that checks this isn't null?
Date: Thursday, March 03, 2016, 10:52:15 PM
From: Thiago Macieira <thiago.macieira at intel.com>
To: development at qt-project.org

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
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
-----------------------------------------
-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160304/cd9c3130/attachment.sig>