Krzysztof Parzyszek 19f420fde1 Consistently use MemoryLocation::UnknownSize to indicate unknown access size ... 1. Change the software pipeliner to use unknown size instead of dropping memory operands. It used to do it before, but MachineInstr::mayAlias did not handle it correctly. 2. Recognize UnknownSize in MachineInstr::mayAlias. 3. Print and parse UnknownSize in MIR. Differential Revision: https://reviews.llvm.org/D50339 llvm-svn: 340208		2018-08-20 20:37:57 +00:00
..
Analysis	[ConstantFolding] improve folding of binops with vector undef operand	2018-08-20 18:19:02 +00:00
Assembler
Bindings
Bitcode
BugPoint
CodeGen	Consistently use MemoryLocation::UnknownSize to indicate unknown access size	2018-08-20 20:37:57 +00:00
DebugInfo	[DebugInfo] In FastISel, convert llvm.dbg.label to DBG_LABEL MI.	2018-08-18 14:55:34 +00:00
Demangle	[MS Demangler] Demangle member pointer template parameters.	2018-08-20 19:15:35 +00:00
Examples
ExecutionEngine
Feature
FileCheck
Instrumentation
Integer
JitListener
Linker
LTO
MC	[AArch64][SVE] Asm: Add SVE System registers	2018-08-20 09:16:59 +00:00
Object
ObjectYAML
Other
SafepointIRVerifier
SymbolRewriter
TableGen
ThinLTO/X86	[ThinLTO] Add option for printing import failure reasons	2018-08-17 16:53:47 +00:00
tools	[llvm-objcopy] Implement -G/--keep-global-symbol(s).	2018-08-17 22:34:48 +00:00
Transforms	ValueTracking: Handle more instructions in isKnownNeverNaN	2018-08-20 16:51:00 +00:00
Unit
Verifier
YAMLParser
.clang-format
CMakeLists.txt
lit.cfg.py
lit.site.cfg.py.in
TestRunner.sh