Lines Matching full:strategy

18 First, you should pick a collector strategy.  LLVM includes a number of built
20 Note that the collector strategy is a description of how LLVM should generate
24 Next, mark your generated functions as using your chosen collector strategy.
61 your final stack maps.  Depending on the collector strategy chosen, this is
188 language.  We try to mitigate this by providing built in collector strategy
201 IR features is specified by the selected :ref:`GC strategy description
211 The ``gc`` function attribute is used to specify the desired GC strategy to the
217 It is the selected GC strategy which defines the exact nature of the code
231 either implementation (on a per :ref:`GC strategy <plugin>` basis).  Longer
251 :ref:`GC strategy <plugin>`.  All calls to ``llvm.gcroot`` **must** reside
343 (although a particular :ref:`collector strategy <plugin>` might).  However, it
347 require the corresponding barrier.  The GC strategy used with such a collector
366 Function's selected :ref:`GC strategy <plugin>`.
382 selected :ref:`GC strategy <plugin>`.
399 To use this collector strategy, mark your functions with:
492 a ``gcroot`` strategy.
510 custom GC strategy around the ``gc.statepoints`` mechanisms, it is recommended
513 This GC strategy does not support read or write barriers.  As a result, these
516 The stack map format generated by this GC strategy can be found in the
531 Support for this GC strategy is a work in progress. This strategy will
533 :ref:`statepoint-example GC<statepoint_example_gc>` strategy in
547 If none of the built in GC strategy descriptions met your needs above, you will