]> granicus.if.org Git - clang/commit
No -fsanitize=function warning when calling noexcept function through non-noexcept...
authorStephan Bergmann <sbergman@redhat.com>
Mon, 18 Dec 2017 13:05:42 +0000 (13:05 +0000)
committerStephan Bergmann <sbergman@redhat.com>
Mon, 18 Dec 2017 13:05:42 +0000 (13:05 +0000)
commit6cd6542e266e963b33dbad009ee963d24eaced16
tree93bf3b4f50b12b470a55fe6ed5115ffb79b12489
parentc61320aee839e9fc461f4646c8506101853f801c
No -fsanitize=function warning when calling noexcept function through non-noexcept pointer in C++17

As discussed in the mail thread <https://groups.google.com/a/isocpp.org/forum/
#!topic/std-discussion/T64_dW3WKUk> "Calling noexcept function throug non-
noexcept pointer is undefined behavior?", such a call should not be UB.
However, Clang currently warns about it.

There is no cheap check whether two function type_infos only differ in noexcept,
so pass those two type_infos as additional data to the function_type_mismatch
handler (with the optimization of passing a null "static callee type" info when
that is already noexcept, so the additional check can be avoided anyway).  For
the Itanium ABI (which appears to be the only one that happens to be used on
platforms that support -fsanitize=function, and which appears to only record
noexcept information for pointer-to-function type_infos, not for function
type_infos themselves), we then need to check the mangled names for occurrence
of "Do" representing "noexcept".

This is the cfe part of a patch covering both cfe and compiler-rt.

Differential Revision: https://reviews.llvm.org/D40720

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@320978 91177308-0d34-0410-b5e6-96231b3b80d8
lib/CodeGen/CGExpr.cpp