Searched refs:RewriteStatepointsForGC (Results 1 – 7 of 7) sorted by relevance
39 RewriteStatepointsForGC.cpp
41 RewriteStatepointsForGC.cpp \
82 struct RewriteStatepointsForGC : public ModulePass { struct85 RewriteStatepointsForGC() : ModulePass(ID) { in RewriteStatepointsForGC() argument128 char RewriteStatepointsForGC::ID = 0;131 return new RewriteStatepointsForGC(); in createRewriteStatepointsForGCPass()134 INITIALIZE_PASS_BEGIN(RewriteStatepointsForGC, "rewrite-statepoints-for-gc",137 INITIALIZE_PASS_END(RewriteStatepointsForGC, "rewrite-statepoints-for-gc",2511 RewriteStatepointsForGC::stripNonValidAttributesFromPrototype(Function &F) { in stripNonValidAttributesFromPrototype()2522 void RewriteStatepointsForGC::stripNonValidAttributesFromBody(Function &F) { in stripNonValidAttributesFromBody()2573 void RewriteStatepointsForGC::stripNonValidAttributes(Module &M) { in stripNonValidAttributes()2586 bool RewriteStatepointsForGC::runOnFunction(Function &F) { in runOnFunction()
3 ;; This test is to verify that RewriteStatepointsForGC correctly relocates values
203 This example was taken from the tests for the :ref:`RewriteStatepointsForGC` utility pass. As such…207 …opt -rewrite-statepoints-for-gc test/Transforms/RewriteStatepointsForGC/basics.ll -S | llc -debug-…631 RewriteStatepointsForGC section in Utility Passes for Safepoint Insertion634 The pass RewriteStatepointsForGC transforms a functions IR by replacing a 667 constructing IR. As currently implemented, RewriteStatepointsForGC must be 670 RewriteStatepointsForGC will ensure that appropriate base pointers are listed681 In practice, RewriteStatepointsForGC can be run much later in the pass 697 RewriteStatepointsForGC and thus does not produce full relocation sequences. argument758 If you are scheduling the RewriteStatepointsForGC pass late in the pass order,
508 :ref:`PlaceSafepoints` and :ref:`RewriteStatepointsForGC` utility passes