tree 9c208bb910919bb7bc01866ddacfb8c3b5ea442c
parent 5434a67468e4c10a0883a1b35a5490a8c0ae88fa
author Konstantin Varlamov <varconst@apple.com> 1637008855 -0800
committer Copybara-Service <copybara-worker@google.com> 1637091042 -0800

[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

GitOrigin-RevId: 434dc0a5bcae50e87458e893ae5469619a35839e