| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[libcxxabi] Copy headers into build location Prior to D120727, the libcxx build was responsible for copying libcxxabi headers into the right location, both in the build and install trees, but now it's the responsibility of the libcxxabi build. While the build already did the right thing for the install tree, it wouldn't copy headers into the build tree, resulting in errors when trying to use the just built toolchain as is the case in the runtimes build when building compiler-rt runtimes. Differential Revision: https://reviews.llvm.org/D125597 | 4 年前 | |
[libcxxabi] Check __SEH__, when checking if ARM EHABI is implied ARM EHABI isn't signalled by any specific compiler builtin define, but is implied by the lack of defines specifying any other exception handling mechanism, __USING_SJLJ_EXCEPTIONS__ or __ARM_DWARF_EH__. As Windows SEH also can be used for unwinding, check for the __SEH__ define too, in the same way. Differential Revision: https://reviews.llvm.org/D126866 | 3 年前 | |
[libcxxabi] Use the right calling convention for exception destructors on i386 Windows On Windows on i386, C++ member functions use a different calling convention ( __thiscall) than the default one for regular functions (__cdecl). (On Windows on architectures other than i386, both calling convention attributes are no-ops.) This matches how libstdc++ declares these types. This fixes the std/thread/futures/futures.{shared,unique}_future/dtor.pass.cpp tests on i386 mingw. Differential Revision: https://reviews.llvm.org/D124990 | 4 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 4 年前 | ||
| 3 年前 | ||
| 4 年前 |