2946cd70 - Update the file headers across all of the LLVM projects in the monorepo

Sat, 19 Jan 2019 08:50:56 +0000

Update the file headers across all of the LLVM projects in the monorepoto reflect the new license.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: 351636 List of files: /llvm-project-15.0.7/llvm/unittests/ADT/IListNodeTest.cpp

085bbf1e - ADT: Add sentinel tracking and custom tags to ilists

Sun, 11 Sep 2016 16:20:53 +0000

ADT: Add sentinel tracking and custom tags to ilistsThis adds two declarative configuration options for intrusive lists(available for simple_ilist, iplist, and ilist). Both of these optionsaffect ilist_node interoperability and need to be passed both to thenode and the list. Instead of adding a new traits class, they'respecified as optional template parameters (in any order).The two options: 1. Pass ilist_sentinel_tracking or ilist_sentinel_tracking to control whether there's a bit on ilist_node "prev" pointer indicating whether it's the sentinel. The default behaviour is to use a bit if and only if LLVM_ENABLE_ABI_BREAKING_CHECKS. 2. Pass ilist_tag and ilist_tag to allow insertion of a single node into two different lists (simultaneously).I have an immediate use-case for (1) ilist_sentinel_tracking: fixing thevalidation semantics of MachineBasicBlock::reverse_iterator to matchilist::reverse_iterator (ala r280032: see the comments at the end of thecommit message there). I'm adding (2) ilist_tag in the same commit tovalidate that the options framework supports expansion. Justin Bognermentioned this might enable a possible cleanup in SelectionDAG, but I'llleave this to others to explore. In the meantime, the unit tests andthe comments for simple_ilist and ilist_node have usage examples.Note that there's a layer of indirection to support optional,out-of-order, template paramaters. Internal classes are templated on aninstantiation of the non-variadic ilist_detail::node_options.User-facing classes use ilist_detail::compute_node_options to computethe correct instantiation of ilist_detail::node_options.The comments for ilist_detail::is_valid_option describe how to add newoptions (e.g., ilist_packed_int).llvm-svn: 281167 List of files: /llvm-project-15.0.7/llvm/unittests/ADT/IListNodeTest.cpp

Changes in IListNodeTest.cpp

2946cd70 - Update the file headers across all of the LLVM projects in the monorepo

085bbf1e - ADT: Add sentinel tracking and custom tags to ilists