| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[libc++] Rename __libcpp_assertion_handler to __libcpp_verbose_abort With the goal of reusing that handler to do other things besides handling assertions (such as terminating when an exception is thrown under -fno-exceptions), the name __libcpp_assertion_handler doesn't really make sense anymore. Furthermore, I didn't want to use the name __libcpp_abort_handler, since that would give the impression that the handler is called whenever std::abort() is called, which is not the case at all. Differential Revision: https://reviews.llvm.org/D130562 (cherry picked from commit 507125af3d0b953cb56bce2e5b8000249fe1ef53) | 3 年前 | |
[libc++] Remove the legacy LIBCXX_LIBCPPABI_VERSION option I think this notion of libc++abi's version was relevant a long time ago on Apple platforms when we were using a Xcode project to build the library. As part of moving Apple's build to CMake, D59489 made it possible to specify the "ABI version" of libc++abi in use. However, it's not possible to build libc++abi with that old ABI anymore and we don't need the ability to link against that version from libc++ anymore. Hence, we can clean this up and stop falsely pretending that libc++abi has more than one ABI version. Differential Revision: https://reviews.llvm.org/D125687 | 4 年前 | |
Effort to reduce the number of exported symbols llvm-svn: 122057 | 15 年前 | |
<rdar://problem/8279559> [libstdcxx] use new linker options to make symbols non-weak llvm-svn: 113616 | 15 年前 | |
[libc++/abi] Revert "[libc++] Move the weak symbols list to libc++abi" This reverts commit c7d4aa711a. I am still investigating the issue, but it looks like that commit has an interaction with ld64 that causes new/delete weak re-exports not to work properly anymore. This is weird because this commit did not touch the exports of new/delete -- I am still investigating. | 5 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 年前 | ||
| 4 年前 | ||
| 15 年前 | ||
| 15 年前 | ||
| 5 年前 |