Require a GC strategy be specified for functions which use gc.statepoint
authorPhilip Reames <listmail@philipreames.com>
Fri, 27 Mar 2015 05:09:33 +0000 (05:09 +0000)
committerPhilip Reames <listmail@philipreames.com>
Fri, 27 Mar 2015 05:09:33 +0000 (05:09 +0000)
commit76acab3fc7bae82a52c22b16d218992982336627
tree157d599e290fbb982be69992010504e6da0ff190
parent28ffcd3f1efe9154f49af695d5a1ff9a3959c58b
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
lib/CodeGen/SelectionDAG/StatepointLowering.cpp
lib/IR/Verifier.cpp
test/Analysis/ValueTracking/memory-dereferenceable.ll
test/CodeGen/Generic/overloaded-intrinsic-name.ll
test/CodeGen/X86/statepoint-invoke.ll
test/CodeGen/X86/statepoint-stack-usage.ll
test/Transforms/CodeGenPrepare/statepoint-relocate.ll
test/Transforms/InstCombine/gc.relocate.ll
test/Transforms/InstCombine/statepoint.ll
test/Transforms/RewriteStatepointsForGC/basics.ll