HomeSort by: relevance | last modified time | path
    Searched defs:Relocate (Results 1 - 2 of 2) sorted by relevancy

  /src/external/apache2/llvm/dist/llvm/lib/Transforms/Scalar/
RewriteStatepointsForGC.cpp 1312 // When inserting gc.relocate and gc.result calls, we need to ensure there are
1314 // the gc.relocate / gc.result call. One case which can arise is a phi node
1331 // At this point, we can safely insert a gc.relocate or gc.result as the first
1427 // Generate the gc.relocate call and save the result
1615 // relocated during copy operation should the GC occur. To relocate the
1806 // Second, create a gc.relocate for every live variable
1849 GCRelocateInst *Relocate = dyn_cast<GCRelocateInst>(U);
1850 if (!Relocate)
1853 Value *OriginalValue = Relocate->getDerivedPtr();
1860 assert(Relocate->getNextNode() &
    [all...]
  /src/external/apache2/llvm/dist/llvm/lib/IR/
Verifier.cpp 2296 // gc.relocate calls which are tied to this statepoint and thus part
2304 "gc.result or gc.relocate are the only value uses "
2312 "gc.relocate connected to wrong gc.statepoint", Call, UserCall);
4926 "gc.relocate must return a pointer or a vector of pointers", Call);
4928 // Check that this relocate is correctly tied to the statepoint
4930 // This is case for relocate on the unwinding path of an invoke statepoint
4944 "gc relocate should be linked to a statepoint", InvokeBB);
4946 // In all other cases relocate should be tied to the statepoint directly.
4951 "gc relocate is incorrectly tied to the statepoint", Call, Token);
4954 // Verify rest of the relocate arguments
    [all...]

Completed in 31 milliseconds