Lines Matching refs:safepoint

69 #. A safepoint is a location at which pointers visible to the compiled
71    change.  After the safepoint completes, the actual pointer value
75   Note that the term 'safepoint' is somewhat overloaded.  It refers to
90    the compiler itself) at the safepoint,
130    reachable after the safepoint,
138 At the most abstract level, inserting a safepoint can be thought of as
164 Depending on our language we may need to allow a safepoint during the execution 
172 ``%obj`` after the safepoint and update any following uses appropriately.  The 
191 safepoint or statepoint.  The statepoint returns a token value (which
270 over the associated call safepoint even if the base is otherwise unused 
290 from the live set at the safepoint entirely.
512 the safepoint sequence of which this ``gc.result`` is a part.
545 at the safepoint.
551 safepoint sequence of which this ``gc.relocation`` is a part.
652 safepoint which could relocate it.  'observably-after' is this usage
655 safepoint.
659 relocated pointer.  Assuming that control flow follows the safepoint,
661 performed before or after the safepoint.  (Remember, the original
662 Value is unmodified by the safepoint.)  The compiler is free to make
696 might contain a safepoint poll with a ``gc.statepoint`` and associated full
769 The pass PlaceSafepoints inserts safepoint polls sufficient to ensure running 
770 code checks for a safepoint request on a timely manner. This pass is expected 
800 In this case, we've added an (unconditional) entry safepoint poll.  Note that 
806 At the moment, PlaceSafepoints can insert safepoint polls at method entry and 
810 PlaceSafepoints includes a number of optimizations to avoid placing safepoint 
815 The implementation of a safepoint poll action is specified by looking up a 
824 you can insert safepoint polls in the frontend.  If you have the later case,