aboutsummaryrefslogtreecommitdiff
path: root/lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp
diff options
context:
space:
mode:
authorStephan Bergmann <sbergman@redhat.com>2017-12-18 13:51:46 +0000
committerStephan Bergmann <sbergman@redhat.com>2017-12-18 13:51:46 +0000
commit2635ea66015955978ff03b917e5f134d3f99a05f (patch)
tree5ae994b18037c5a42ace92d22e14f72c50ecb26d /lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp
parent8ee540c01a84db7a9640b5c8e8953a5209d02de6 (diff)
downloadllvm-2635ea66015955978ff03b917e5f134d3f99a05f.zip
llvm-2635ea66015955978ff03b917e5f134d3f99a05f.tar.gz
llvm-2635ea66015955978ff03b917e5f134d3f99a05f.tar.bz2
Revert r320977 "No -fsanitize=function warning when calling noexcept function through non-noexcept pointer in C++17"
At least <http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-android/ builds/6013/steps/annotate/logs/stdio> complains about __ubsan::__ubsan_handle_function_type_mismatch_abort (compiler-rt lib/ubsan/ubsan_handlers.cc) returning now despite being declared 'noreturn', so looks like a different approach is needed for the function_type_mismatch check to be called also in cases that may ultimately succeed. llvm-svn: 320981
Diffstat (limited to 'lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp')
0 files changed, 0 insertions, 0 deletions