aboutsummaryrefslogtreecommitdiff
path: root/lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp
diff options
context:
space:
mode:
authorStephan Bergmann <sbergman@redhat.com>2017-12-18 13:05:42 +0000
committerStephan Bergmann <sbergman@redhat.com>2017-12-18 13:05:42 +0000
commitf4e4daeaf10e4f27e060893b0af254962948144c (patch)
tree867abce121bde768761f9f03f6d94fcb8ec5e728 /lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp
parentc7121f6d28e3d12b439851f935c1da169dc18167 (diff)
downloadllvm-f4e4daeaf10e4f27e060893b0af254962948144c.zip
llvm-f4e4daeaf10e4f27e060893b0af254962948144c.tar.gz
llvm-f4e4daeaf10e4f27e060893b0af254962948144c.tar.bz2
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 llvm-svn: 320978
Diffstat (limited to 'lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp')
0 files changed, 0 insertions, 0 deletions