Konstantin Varlamov 434dc0a5bc [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

2021-11-16 11:23:27 -08:00

..

abi

[libc++] Always define a key function for std::bad_function_call in the dylib

2021-11-16 11:23:27 -08:00

libc++abi.v1.exp

[libc++] Fix the no-exceptions build of libc++ on Apple

2020-04-20 10:45:14 -04:00

libc++abi.v2.exp

[libc++] Fix the no-exceptions build of libc++ on Apple

2020-04-20 10:45:14 -04:00

libc++unexp.exp

…

notweak.exp

…

weak.exp

[libc++/abi] Revert "[libc++] Move the weak symbols list to libc++abi"

2020-10-05 11:42:13 -04:00