diff options
author | Konstantin Varlamov <varconst@apple.com> | 2021-11-15 12:40:55 -0800 |
---|---|---|
committer | Konstantin Varlamov <varconst@apple.com> | 2021-11-16 11:23:27 -0800 |
commit | 434dc0a5bcae50e87458e893ae5469619a35839e (patch) | |
tree | 9e6ff643d2907b520df81783330c317c071482dc /lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.h | |
parent | c95a9f46c9cff8377232466e9bb6f097893fc860 (diff) | |
download | llvm-434dc0a5bcae50e87458e893ae5469619a35839e.zip llvm-434dc0a5bcae50e87458e893ae5469619a35839e.tar.gz llvm-434dc0a5bcae50e87458e893ae5469619a35839e.tar.bz2 |
[libc++] Always define a key function for std::bad_function_call in the dylib
However, whether applications rely on the std::bad_function_call vtable
being in the dylib is still controlled by the ABI macro, since changing
that would be an ABI break.
Also separate preprocessor definitions for whether to use a key function
and whether to use a `bad_function_call`-specific `what` message
(`what` message is mandated by [LWG2233](http://wg21.link/LWG2233)).
Differential Revision: https://reviews.llvm.org/D92397
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.h')
0 files changed, 0 insertions, 0 deletions