Changes in typeinfo

385cc25a - [libc++] Ensure that all public C++ headers include <__assert>

Fri, 25 Mar 2022 16:55:36 +0000

[libc++] Ensure that all public C++ headers include <__assert>This patch changes the requirement for getting the declaration of theassertion handler from including <__assert> to including any publicC++ header of the library. Note that C compatibility headers areexcluded because we don't implement all the C headers ourselves --some of them are taken straight from the C library, like assert.h.It also adds a generated test to check it. Furthermore, this newgenerated test is designed in a way that will make it possible toreplace almost all the existing test-generation scripts with thissystem in upcoming patches.Differential Revision: https://reviews.llvm.org/D122506 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

fa6b9e40 - [libc++] Normalize all our '#pragma GCC system_header', and regression-test.

Wed, 02 Feb 2022 01:16:40 +0000

[libc++] Normalize all our '#pragma GCC system_header', and regression-test.Now we'll notice if a header forgets to include this magic phrase.Differential Revision: https://reviews.llvm.org/D118800 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

d2b0df35 - [libc++][NFC] Update namespace comments in include/

Thu, 02 Dec 2021 13:12:51 +0000

[libc++][NFC] Update namespace comments in include/update the namspace comments in include/Reviewed By: ldionne, #libcSpies: smeenai, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D114947 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

eb8650a7 - [runtimes][NFC] Remove filenames at the top of the license notice

Wed, 17 Nov 2021 21:25:01 +0000

[runtimes][NFC] Remove filenames at the top of the license noticeWe've stopped doing it in libc++ for a while now because these nameswould end up rotting as we move things around and copy/paste stuff.This cleans up all the existing files so as to stop the spreadingas people copy-paste headers around. List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

8d5c0b87 - [libc++] Remove unnecessary reinterpret_cast from typeinfo

Mon, 28 Jun 2021 13:53:28 +0000

[libc++] Remove unnecessary reinterpret_cast from typeinfoIn typeinfo there is a reinterpret_cast between a uintptr_t and size_t. These are two integer types and therefore a reinterpret_cast is not right for this situation. It looks like it may have been copied and pasted from above in the file. An implicit cast works in it's place.Reviewed By: ldionne, #libcDifferential Revision: https://reviews.llvm.org/D104814 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

bfbd73f8 - [libc++] Alphabetize and include-what-you-use. NFCI.

Wed, 19 May 2021 15:57:04 +0000

[libc++] Alphabetize and include-what-you-use. NFCI.Differential Revision: https://reviews.llvm.org/D102781 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

4cd6ca10 - [libc++] NFC: Normalize `#endif //` comment indentation

Tue, 20 Apr 2021 16:03:32 +0000

[libc++] NFC: Normalize `#endif //` comment indentation List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

17095dc8 - [libc++][NFC] Increase readability of typeinfo comparison of ARM64

Tue, 02 Mar 2021 21:18:37 +0000

[libc++][NFC] Increase readability of typeinfo comparison of ARM64We wasted a good deal of time trying to figure out whether our implementationwas correct. In the end, it was, but it wasn't so easy to determine. Thispatch dumbs down the implementation and improves the documentation to makeit easier to validate.See https://lists.llvm.org/pipermail/libcxx-dev/2020-December/001060.html.Differential Revision: https://reviews.llvm.org/D97802 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

d586f92c - [libc++] Consistently replace `std::` qualification with `_VSTD::` or nothing. NFCI.

Fri, 27 Nov 2020 16:02:06 +0000

[libc++] Consistently replace `std::` qualification with `_VSTD::` or nothing. NFCI.I used a lot of `git grep` to find places where `std::` was being usedoutside of comments and assert-messages. There were three outcomes:- Qualified function calls, e.g. `std::move` becomes `_VSTD::move`. This is the most common case.- Typenames that don't need qualification, e.g. `std::allocator` becomes `allocator`. Leaving these as `_VSTD::allocator` would also be fine, but I decided that removing the qualification is more consistent with existing practice.- Names that specifically need un-versioned `std::` qualification, or that I wasn't sure about. For example, I didn't touch any code in , , , or any ext/ or experimental/ headers; and I didn't touch any instances of `std::type_info`.In some deduction guides, we were accidentally using `class Alloc = typename std::allocator`,despite `std::allocator`'s type-ness not being template-dependent.Because `std::allocator` is a qualified name, this did parse as we intended;but what we meant was simply `class Alloc = allocator`.Differential Revision: https://reviews.llvm.org/D92250 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

be00e889 - [libc++] Clarify how we pick the typeinfo comparison

Mon, 16 Nov 2020 23:13:43 +0000

[libc++] Clarify how we pick the typeinfo comparisonThis commit makes it clear that the typeinfo comparison implementationis automatically selected by default, and that the CMake option onlyoverrides the value. This has been a source of confusion and bugs eversince we've introduced complexity in that area, so I'm trying to simplifyit while still allowing for some control on the implementation.Differential Revision: https://reviews.llvm.org/D91574 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

2eadbc86 - [libc++] Rework the whole availability markup implementation

Wed, 04 Nov 2020 20:01:25 +0000

[libc++] Rework the whole availability markup implementationCurrently, vendor-specific availability markup is enabled by default.This means that even when building against trunk libc++, the headerswill by default prevent you from using some features that were notreleased in the dylib on your target platform. This is a source offrustration since people building libc++ from sources are usually nottrying to use some vendor's released dylib.For that reason, I've been thinking for a long time that availabilityannotations should be off by default, which is the primary change thatthis commit enables.In addition, it reworks the implementation to make it easier for newvendors to add availability annotations for their platform, and itrefreshes the documentation to reflect the current state of the codebase.Finally, a CMake configuration option is added to control whetheravailability annotations should be turned on for the flavor of libc++being created. The intent is for vendors like Apple to turn it on, andfor the upstream libc++ to leave it off (the default).Differential Revision: https://reviews.llvm.org/D90843 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

d0fcdcd2 - [libc++] Fix the LIBCXX_HAS_MERGED_TYPEINFO_NAMES_DEFAULT setting

Fri, 15 May 2020 19:58:19 +0000

[libc++] Fix the LIBCXX_HAS_MERGED_TYPEINFO_NAMES_DEFAULT settingWhen the __config_site header is generated, but LIBCXX_HAS_MERGED_TYPEINFO_NAMES_DEFAULTwasn't specified, _LIBCPP_HAS_MERGED_TYPEINFO_NAMES_DEFAULT would be definedto 0, which was the NonUnique RTTI comparison implementation. The intentwas to use the Unique RTTI comparison implementation in that case, whichcaused https://llvm.org/PR45549.Instead, use a proper "switch" to select the RTTI comparison implementation.Note that 0 can't be used as a value, because that is treated the sameby CMake as a variable that is just not defined.Differential Revision: https://reviews.llvm.org/D80037 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

585a3cc3 - Fix -Wdeprecated-copy-dtor and -Wdeprecated-dynamic-exception-spec warnings.

Fri, 13 Mar 2020 18:36:26 +0000

Fix -Wdeprecated-copy-dtor and -Wdeprecated-dynamic-exception-spec warnings.Summary:The former are like:libcxx/include/typeinfo:322:11: warning: definition of implicit copy constructor for 'bad_cast' is deprecated because it has a user-declared destructor [-Wdeprecated-copy-dtor] virtual ~bad_cast() _NOEXCEPT; ^libcxx/include/typeinfo:344:11: note: in implicit copy constructor for 'std::bad_cast' first required here throw bad_cast(); ^Fix these by adding an explicitly defaulted copy constructor.The latter are like:libcxx/include/codecvt:105:37: warning: dynamic exception specifications are deprecated [-Wdeprecated-dynamic-exception-spec] virtual int do_encoding() const throw(); ^~~~~~~Fix these by using the _NOEXCEPT macro instead.Reviewers: EricWF, mclow.lists, ldionne, #libcReviewed By: EricWF, #libcSubscribers: dexonsmith, libcxx-commitsTags: #libcDifferential Revision: https://reviews.llvm.org/D76150 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

e337fb07 - add type_traits include as required for std::integral_constant

Fri, 14 Feb 2020 15:38:16 +0000

add type_traits include as required for std::integral_constant List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

82705e7d - Fix build breakage on 32-bit machines

Wed, 29 May 2019 02:38:19 +0000

Fix build breakage on 32-bit machinesllvm-svn: 361917 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

2405bd68 - Rework std::type_info definition to support systems without fully

Wed, 29 May 2019 02:21:37 +0000

Rework std::type_info definition to support systems without fullymerged type info names.Previously std::type_info always expected type info string to be unique.But this isn't always the case. Like when -Bsymbolic is passed to thelinker or due to llvm.org/PR37398.This patch adds the LIBCXX_HAS_MERGED_TYPEINFO_NAMES_DEFAULT CMakeoption which, when specified, overrides the default configuration forthe library.The current defaults still assume unique names even though this isn'tstrictly correct for ELF binaries. We should consider changing thedefault in a follow up commit.llvm-svn: 361913 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

e69290dc - Make VCRuntime ABI configuration a first-class option.

Tue, 05 Mar 2019 01:57:01 +0000

Make VCRuntime ABI configuration a first-class option.Summary:On Windows we currently provide two separate ABI configurations. One which defers to `vcruntime` to provide the C++ runtime and another which doesn't.Using `vcruntime` allows interoperability which programs compiled against the MSVC STL, and should be preferred whenever possible.When deferring to `vcruntime` much of the ABI we provide changes. Including the layout of `` types, their vtables, and how the linkage of their members.This patch introduces the `_LIBCPP_ABI_VCRUNTIME` macro to denote this configuration. It also cleans up the existing configuration for using `vcruntime`.This cleanup lays the groundwork for fixing a number of ABI and interoperability bugs in ``.Reviewers: thomasanderson, ldionne, smeenaiReviewed By: smeenaiSubscribers: jdoerfert, libcxx-commits, #libcDifferential Revision: https://reviews.llvm.org/D58942llvm-svn: 355366 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

6b653fc7 - [libc++] Disentangle the 3 implementations of type_info

Fri, 01 Feb 2019 20:00:13 +0000

[libc++] Disentangle the 3 implementations of type_infoSummary:We currently have effectively 3 implementations of type_info: one forthe Microsoft ABI, one that does not assume that there's a unique copyof each RTTI in a progran, and one that assumes a unique copy.Those 3 implementations are entangled into the same class with nestedifdefs, which makes it very difficult to understand. Furthermore, thebenefit of doing this is rather small since the code that is duplicatedacross implementations is just a couple of trivial lines.This patch stamps out the 3 versions of type_info explicitly to increasereadability. It also explains what's going on with short comments, becauseit's far from obvious.Reviewers: EricWF, mclow.listsSubscribers: christof, jkorous, dexonsmithDifferential Revision: https://reviews.llvm.org/D57606llvm-svn: 352905 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

57b08b09 - Update more file headers across all of the LLVM projects in the monorepo

Sat, 19 Jan 2019 10:56:40 +0000

Update more file headers across all of the LLVM projects in the monorepoto reflect the new license. These used slightly different spellings thatdefeated my regular expressions.We understand that people may be surprised that we're moving the headerentirely to discuss the new license. We checked this carefully with theFoundation's lawyer and we believe this is the correct approach.Essentially, all code in the project is now made available by the LLVMproject under our new license, so you will see that the license headersinclude that license only. Some of our contributors have contributedcode under our old license, and accordingly, we have retained a copy ofour old license notice in the top-level files in each project andrepository.llvm-svn: 351648 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo

9f3561c2 - [libcxx] Remove unused macro _LIBCPP_HAS_UNIQUE_TYPEINFO

Fri, 21 Dec 2018 20:14:43 +0000

[libcxx] Remove unused macro _LIBCPP_HAS_UNIQUE_TYPEINFOSummary:We already have the negation of that as _LIBCPP_HAS_NONUNIQUE_TYPEINFO.Having both defined is confusing, since only one of them is used.Reviewers: EricWF, mclow.listsSubscribers: christof, jkorous, dexonsmith, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D54537llvm-svn: 349947 List of files: /llvm-project-15.0.7/libcxx/include/typeinfo