[libc++] Always define a key function for std::bad_function_call in the dylib
authorLouis Dionne <ldionne.2@gmail.com>
Tue, 2 Nov 2021 19:14:48 +0000 (12:14 -0700)
committerKonstantin Varlamov <varconst@apple.com>
Mon, 8 Nov 2021 08:31:00 +0000 (00:31 -0800)
commitbc74231756d6c317505a9fa4c5a269134687ae56
tree2fc76b21a2a0599aec1537d15701a0c81d360cc8
parenta0633f5ccb04e4b1613eeb23af10ad729dace2b5
[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.

Differential Revision: https://reviews.llvm.org/D92397
libcxx/include/__config
libcxx/lib/abi/CHANGELOG.TXT
libcxx/lib/abi/x86_64-apple-darwin.libcxxabi.v1.stable.exceptions.no_new_in_libcxx.abilist
libcxx/lib/abi/x86_64-unknown-linux-gnu.libcxxabi.v1.stable.exceptions.no_new_in_libcxx.abilist