Lines Matching full:runtime
12 In this document we refer to the "runtime" collectively as all
19 values that the runtime requires to be live at this point. For
20 example, they may be the values the runtime will need to resume
34 generation, which allows the runtime to locate the patchpoint and
41 in a variety of settings, the most obvious being a runtime (JIT)
63 richer information to a garbage collecting runtime, but that usage
80 runtime patches code at the stack map's address, it will destructively
90 the runtime to uniquely identify the stack map, and the offset within
130 The stack map ID allows a runtime to locate the desired stack map
137 ``llvm.experimental.patchpoint`` may occur. This allows the runtime to
144 the runtime does not need to consider this corner case.
150 call void @runtime()
168 Now, if the runtime needs to invalidate the compiled code, it may
177 This way, after the normal call to the runtime returns, the code will
247 The runtime may patch the code emitted for the patch point, including
248 the call sequence and nops. However, the runtime may not assume
250 patching is not allowed. The runtime must patch all reserved bytes,
367 as ``Indirect`` locations. The runtime must load those values from a
379 be saved by the runtime. This is an important optimization when the
385 specific subregister information. Instead the runtime must interpret
388 ``%ah``. It doesn't matter in practice, because the runtime will
390 ``%ymm0``, then the runtime can safely optimize by saving only
394 the runtime. It is currently experimental and may change in the short
395 term, but minimizing the need to update the runtime is
398 secondary because the runtime is expected to parse the data
400 own format. Since the runtime controls the allocation of sections, it
430 any higher-level entity. The runtime must be able to interpret the
438 An important motivation for this design is to allow a runtime to
440 associated with a stack map. The runtime must be able to rebuild a
448 above a stack map could be invalid. For example, the runtime may
452 becomes unsafe. The runtime can prevent subsequent execution of that
454 the current call site and the load (typically, the runtime would
457 program could crash before the runtime could take back control.
472 that the runtime requested. This differs from Indirect locations,
485 The runtime can determine this alloca's relative location on the
487 differs from Register and Indirect locations, because the runtime can
495 value. This can be verified by the runtime simply by checking that the
