Philip Reames 76acab3fc7 Require a GC strategy be specified for functions which use gc.statepoint ... This was discussed a while back and I left it optional for migration. Since it's been far more than the 'week or two' that was discussed, time to actually make this manditory. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@233357 91177308-0d34-0410-b5e6-96231b3b80d8		2015-03-27 05:09:33 +00:00
..
Analysis	Require a GC strategy be specified for functions which use gc.statepoint	2015-03-27 05:09:33 +00:00
Assembler	Verifier: Check accessors of MDLocation	2015-03-26 22:05:04 +00:00
Bindings
Bitcode
BugPoint	bugpoint: Verify input files	2015-03-26 05:03:10 +00:00
CodeGen	Require a GC strategy be specified for functions which use gc.statepoint	2015-03-27 05:09:33 +00:00
DebugInfo	DebugInfo: Update testcases with invalid variables	2015-03-27 01:58:34 +00:00
ExecutionEngine	Make exit-code test use same mechanism as existing one.	2015-03-25 14:35:40 +00:00
Feature
FileCheck
Instrumentation
Integer
JitListener
Linker	Verifier: Check accessors of MDLocation	2015-03-26 22:05:04 +00:00
LTO
MC	[AsmPrinter] Don't assert on GOT equivalent non-constant users.	2015-03-27 01:40:54 +00:00
Object
Other
SymbolRewriter
TableGen
tools
Transforms	Require a GC strategy be specified for functions which use gc.statepoint	2015-03-27 05:09:33 +00:00
Unit
Verifier
YAMLParser
.clang-format
CMakeLists.txt	test: Fix the dependencies for the check-llvm-* targets	2015-03-25 08:07:47 +00:00
lit.cfg
lit.site.cfg.in
Makefile
Makefile.tests
TestRunner.sh