Lines Matching refs:gcroot
62 accomplished by using either the ``@llvm.gcroot`` intrinsics or an
97 :ref:`processor stack and registers <gcroot>`.
229 compiled code at safepoints. ``llvm.gcroot`` is the older mechanism;
232 term, we will probably either migrate away from ``llvm.gcroot`` entirely, or
246 void @llvm.gcroot(i8** %ptrloc, i8* %metadata)
248 The ``llvm.gcroot`` intrinsic is used to inform LLVM that a stack variable
251 :ref:`GC strategy <plugin>`. All calls to ``llvm.gcroot`` **must** reside
261 respective ``gcroot`` before every call site and reloaded after every call.
263 SSA form need only add a call to ``@llvm.gcroot`` for those variables which
266 It is also important to mark intermediate values with ``llvm.gcroot``. For
269 initialized and marked with ``llvm.gcroot`` in function's prologue.
298 call void @llvm.gcroot(i8** %tmp, i8* null)
336 ;; Load the object pointer from a gcroot.
440 /// @llvm.gcroot is null.
463 /// @llvm.gcroot.
487 LLVM ships with two example collectors which leverage the ``gcroot``
490 in writing an ``gcroot`` compatible GC plugin. In particular, these are the
492 a ``gcroot`` strategy.
699 | *gcroot* | |v| | |x| | |x| | | | | | |
804 ``@llvm.gcroot`` intrinsic.
832 If the ``llvm.gcroot`` intrinsic is eliminated before code generation by a
871 sequences. Using gcroot, all call instructions are inferred to be possible