Eli Friedman cfeebf9848 Remove SequentialType from the type heirarchy. ... Now that we have scalable vectors, there's a distinction that isn't getting captured in the original SequentialType: some vectors don't have a known element count, so counting the number of elements doesn't make sense. In some cases, there's a better way to express the commonality using other methods. If we're dealing with GEPs, there's GEP methods; if we're dealing with a ConstantDataSequential, we can query its element type directly. In the relatively few remaining cases, I just decided to write out the type checks. We're talking about relatively few places, and I think the abstraction doesn't really carry its weight. (See thread "[RFC] Refactor class hierarchy of VectorType in the IR" on llvmdev.) Differential Revision: https://reviews.llvm.org/D75661		2020-04-06 17:03:49 -07:00
..
CMakeLists.txt	[cmake] Explicitly mark libraries defined in lib/ as "Component Libraries"	2019-11-21 10:48:08 -08:00
IRMover.cpp	Remove SequentialType from the type heirarchy.	2020-04-06 17:03:49 -07:00
LinkDiagnosticInfo.h
LinkModules.cpp	[Alignment][NFC] Remove dependency on GlobalObject::setAlignment(unsigned)	2019-10-15 11:24:36 +00:00
LLVMBuild.txt