Lines Matching refs:GC

356 GC Transitions
366 statepoint may be marked as a GC transition, and data that is necessary to
370   Note that although in many cases statepoints may be inferred to be GC
372   function with GC strategy "foo" to a function with GC strategy "bar"),
373   indirect calls that are also GC transitions must also be supported. This
374   requirement is the driving force behind the decision to require that GC
378 as a GC transition. Depending on our target, the transition code may need to
380 Let's assume a hypothetical GC--somewhat unimaginatively named "hypothetical-gc"
429 strategy-specific lowering is not present, and all GC transitions are emitted as
585 that the ``statepoint-example`` GC strategy uses to distinguish references from
630 RewriteStatepointsForGC performs GC specific lowering for the following
639 GC leaf lowering and GC parseable lowering. If a call is explicitly marked with
640 "gc-leaf-function" attribute the call is lowered to a GC leaf call to
643 take a safepoint. Otherwise, the call is made GC parseable by wrapping the
645 copy operation. Note that a GC parseable copy operation is not required to
649 GC parseable calls to '``llvm.memcpy.element.unordered.atomic.*``',
656 GC parseable lowering also involves adjusting the arguments for the call.