Lines Matching refs:stackmap

25 :ref:`stackmap-section`. This stack map data contains a record for
70 maps and patch points: ``llvm.experimental.stackmap`` and
75 call to ``llvm.experimental.stackmap``). The choice of which to use
78 to calling conventions. ``llvm.experimental.stackmap`` does not
89 in the :ref:`stackmap-section`. The record includes an ID, allowing
93 '``llvm.experimental.stackmap``' Intrinsic
102         @llvm.experimental.stackmap(i64 <id>, i32 <numShadowBytes>, ...)
107 The '``llvm.experimental.stackmap``' intrinsic records the location of
136 another call to ``llvm.experimental.stackmap`` or
151   call void (i64, i32, ...)* @llvm.experimental.stackmap(i64 77, i32 8,
231 ``llvm.experimental.stackmap.*``. The difference is that space will
316 Module forces code emission to create a :ref:`stackmap-section`. The
387 are the registers that are live across the stackmap and therefore must
393 number and size in bytes. The stackmap format deliberately omits
395 this information conservatively. For example, if the stackmap reports
398 simply save ``%rax``. However, if the stackmap reports 16 bytes at
471 To enforce these semantics, stackmap and patchpoint intrinsics are
482 As shown in :ref:`stackmap-section`, a Direct stack map location
495     llvm.experimental.stackmap(i64 <ID>, i32 <shadowBytes>, i64* %a)