[all-commits] [llvm/llvm-project] bc7423: [libc++] Always define a key function for std::bad...
Louis Dionne via All-commits
all-commits at lists.llvm.org
Mon Nov 8 00:41:22 PST 2021
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: bc74231756d6c317505a9fa4c5a269134687ae56
https://github.com/llvm/llvm-project/commit/bc74231756d6c317505a9fa4c5a269134687ae56
Author: Louis Dionne <ldionne.2 at gmail.com>
Date: 2021-11-08 (Mon, 08 Nov 2021)
Changed paths:
M libcxx/include/__config
M libcxx/lib/abi/CHANGELOG.TXT
M libcxx/lib/abi/x86_64-apple-darwin.libcxxabi.v1.stable.exceptions.no_new_in_libcxx.abilist
M libcxx/lib/abi/x86_64-unknown-linux-gnu.libcxxabi.v1.stable.exceptions.no_new_in_libcxx.abilist
Log Message:
-----------
[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
More information about the All-commits
mailing list