bcm5719-llvm/libcxxabi, branch meklort-10.0.1Project Ortega BCM5719 LLVMhttps://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.12020-04-13T14:13:36+00:00Bump version to 10.0.12020-04-13T14:13:36+00:00Tom Stellardtstellar@redhat.com2020-04-08T14:22:49+00:00urn:sha1:4822f2a6154742ab24e0266d6c4b0c2937d22ab7Drop git version suffix2020-02-17T22:47:30+00:00Aaron Puchertaaronpuchert@alice-dsl.net2020-02-17T22:47:28+00:00urn:sha1:4f53867ec27bde33479c7891c256225f2075945a
Summary: Also fix the version for libcxxabi, which was stuck in the past.
Reviewers: hans, mclow.lists
Reviewed By: hans
Subscribers: mgorny, christof, libcxx-commits, llvm-commits, ldionne
Tags: #libc, #llvm
Differential Revision: https://reviews.llvm.org/D74586
[libcxxabi] Fix layout of __cxa_exception for win642020-02-04T09:56:52+00:00Martin Storsjömartin@martin.st2020-02-01T11:32:57+00:00urn:sha1:165a6367631d643f8f186d7a809013652cf321d6
Win64 isn't LP64, it's LLP64, but there's no __LLP64__ predefined -
just check _WIN64 in addition to __LP64__.
This fixes compilation after static asserts about the struct layout
were added in f2a436058fcbc11291e73badb44e243f61046183.
Differential Revision: https://reviews.llvm.org/D73838
(cherry picked from commit 09dc884eb2e4a433eb8c5ed20a17108091279295)
[libcxxabi] Insert padding in __cxa_exception struct for compatibility2020-02-03T13:07:11+00:00Steven Wustevenwu@apple.com2020-01-30T18:02:23+00:00urn:sha1:674ec1eb16678b8addc02a4b0534ab383d22fa77
Summary:
Preserve the old ABI for __cxa_exception and __cxa_dependent_exception
on 64 bit platforms or ARM_EHABI platforms.
After r276215, libunwind in llvm-project labels _Unwind_Exception to be
double word aligned. That change implictly adds a padding before
unwindHeader field in __cxa_exception and __cxa_dependent_exception.
Preserve the same negative offsets in those struct by moving the padding
to the beginning of the field.
The assumption here is that if the ABI is not aware of the padding before
unwindHeader and put the referenceCount/primaryException in there, no padding
should exist before unwindHeader.
Reviewers: EricWF, mclow.lists, ldionne, jroelofs, dexonsmith, rjmccall, compnerd, phosek, ahatanak
Reviewed By: rjmccall
Subscribers: hans, smeenai, kristof.beyls, christof, jkorous, ributzka, libcxx-commits
Tags: #libc
Differential Revision: https://reviews.llvm.org/D72543
(cherry picked from commit f2a436058fcbc11291e73badb44e243f61046183)
[demangle] Copy back some NFC commits from LLVM2020-01-09T18:27:24+00:00Erik Pilkingtonerik.pilkington@gmail.com2020-01-09T18:24:09+00:00urn:sha1:183b5d38d7cffc10ff9f4914b8879ed5b1976e40[libcxxabi] Allow tests to link with static libc++abi/libc++ even if the shared version is present2020-01-09T16:01:57+00:00Sergej Jaskiewiczjaskiewiczs@icloud.com2019-12-26T09:28:39+00:00urn:sha1:fb76c7934dce2ede7e04097edb455eba58f6ebfd
Summary:
Right now the only way to force libc++abi tests to link with the static version of libc++abi is to set `LIBCXXABI_ENABLE_SHARED` to `OFF`. However, this doesn't work when libc++abi is built as standalone project because of [this](https://github.com/llvm/llvm-project/blob/54c522420347e58aa7bae1892cf5c5672b57c875/libcxxabi/CMakeLists.txt#L503-L519).
This change allows specifying the version of the library for tests to link with.
This is useful for remote testing, for example, with `SSHExecutor`, where we _have_ to link with libc++abi statically.
Two new CMake options are introduced here: `LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXXABI` and `LIBCXXABI_LINK_TESTS_WITH_SHARED_LIBCXX`. They can be set to `OFF` to tell the test utility to link tests with the static libraries.
It shouldn't break anything, because the default values of these options are set such that the test utility will behave the same way.
Reviewers: EricWF, mclow.lists, phosek, mehdi_amini, ldionne, jroelofs, bcraig
Subscribers: mgorny, christof, ldionne, libcxx-commits
Tags: #libc
Differential Revision: https://reviews.llvm.org/D71894
[libc++abi] Fix non-constant initialization of default terminate2019-12-12T01:32:14+00:00Eric Fiseliereric@efcs.ca2019-12-12T01:32:14+00:00urn:sha1:a9245e4f86165ac38a297138fff08cd4eb7255a7
handlers.
[libcxx{,abi}] Don't link libpthread and libdl on Fuchsia2019-12-06T19:15:15+00:00Petr Hosekphosek@google.com2019-12-06T19:11:31+00:00urn:sha1:1aa17023819216dae77c7798510f178dae07a57f
These are a part of the libc so linking these explicitly isn't necessary
and embedding these as deplibs causes link time error.
This issues was introduced in a9b5fff which changed how we emit deplibs.
Differential Revision: https://reviews.llvm.org/D71135
[libcxx{,abi}] Emit deplibs only when detected by CMake2019-12-02T21:19:20+00:00Michał Górnymgorny@gentoo.org2019-12-02T10:49:20+00:00urn:sha1:a9b5fff591d462f1f22e44ab1a269b82b8f2a664
This is a followup to 35bc5276ca3. It fixes the dependent libs usage
in libcxx and libcxxabi to link pthread and rt libraries only if CMake
detects them, rather than based on explicit platform blacklist.
Differential Revision: https://reviews.llvm.org/D70888
[libcxxabi] Prevent cmake from removing our explicit system C++ include paths2019-11-12T18:08:40+00:00Sam Cleggsbc@chromium.org2019-11-07T22:51:25+00:00urn:sha1:4230fa939021e7a85f3ec06a4b1d8c661dfe329b
We build with `-nostdinc++` and add our own header path via
`LIBCXXABI_LIBCXX_INCLUDES`. However cmake tried to be clever and if
`LIBCXXABI_LIBCXX_INCLUDES` happens to match the compilers system path
it will remove the `-I` flag meaning we can't access any C++ headers.
Ideally cmake would be able see that we are using `-nostdinc++` and
disable this behaviour.
Differential Revision: https://reviews.llvm.org/D69973