Home
last modified time | relevance | path

Searched refs:patching (Results 1 – 20 of 20) sorted by relevance

/llvm-project-15.0.7/compiler-rt/test/xray/TestCases/Posix/
H A Dcoverage-sample.cpp20 thread_local bool patching = false; in coverage_handler() local
21 if (patching) return; in coverage_handler()
22 patching = true; in coverage_handler()
25 patching = false; in coverage_handler()
/llvm-project-15.0.7/llvm/docs/
H A DStackMaps.rst31 patching a new instruction sequence at run time. Patch points look
50 used whenever stack maps or code patching are needed. Because the
72 stack map record, and they both allow some form of code patching. They
76 depends on whether it is necessary to reserve space for code patching
83 patching without overwriting surrounding code. The
118 To use this intrinsic as a bare-bones stack map, with no code patching
141 be overwritten by destructive patching. Without shadow bytes, this
142 destructive patching could overwrite program text or data outside the
232 still be reserved for patching, a call will be emitted, and a return
255 patching is not allowed. The runtime must patch all reserved bytes,
[all …]
H A DFaultMaps.rst115 null checks via code patching or recompilation. It follows that there
H A DHowToBuildWindowsItaniumPrograms.rst54 that runs after IAT patching but before anything that might use the vtable pointers,
H A DXRayFDRFormat.rst141 | | | patching and as a lookup into the binary's |
H A DXRay.rst147 the runtime components that perform the patching and unpatching of inserted
H A DHowToReleaseLLVM.rst317 Below are the rules regarding patching the release branch:
H A DGarbageCollection.rst216 using either the loadable plugin mechanism, or by patching your copy of LLVM.
H A DLangRef.rst351 "``anyregcc``" - Dynamic calling convention for code patching
352 This is a special convention that supports patching an arbitrary code
1481 function hot-patching and instrumentation.
1893 function is intended to support patching a function prologue to
1909 patching may have to be separately conveyed via the linkage type.
12437 sequence after patching is expected to represent an operation
24579 LLVM provides experimental intrinsics to support runtime patching
/llvm-project-15.0.7/lld/test/ELF/
H A Dx86-64-reloc-32.s12 ## Check patching of negative addends
H A Dx86-64-reloc-pc32.s12 ## Check patching of negative addends
/llvm-project-15.0.7/llvm/test/Transforms/ADCE/
H A D2003-04-25-PHIPostDominateProblem.ll3 ; PHI node is dead, so we just avoid patching up dead PHI nodes.
/llvm-project-15.0.7/llvm/test/tools/llvm-objcopy/COFF/
H A Ddebug-entry-no-payload.test3 ## IMAGE_DEBUG_TYPE_UNKNOWN) when patching entries that may have moved during
/llvm-project-15.0.7/llvm/docs/CommandGuide/
H A Dllvm-objdump.rst219 When printing relocations, only print the relocations patching offsets from at least ``address``.
227 When printing relocations, only print the relocations patching offsets up to ``address``.
/llvm-project-15.0.7/llvm-libgcc/docs/
H A DLLVMLibgcc.rst45 We alternatively considered patching glibc so that the source doesn't directly
/llvm-project-15.0.7/compiler-rt/
H A DCMakeLists.txt52 option(COMPILER_RT_BUILD_XRAY_NO_PREINIT "Build xray with no preinit patching" OFF)
/llvm-project-15.0.7/llvm/lib/Target/X86/
H A DX86.td347 // environments such as a kernel that does boot-time hot patching.
/llvm-project-15.0.7/mlir/docs/Bindings/
H A DPython.md1002 (you are always free to do ad-hoc patching in your `{DIALECT_NAMESPACE}.py` file
/llvm-project-15.0.7/clang/include/clang/Basic/
H A DAttrDocs.td5193 the beginning and exit points to allow for runtime patching.
/llvm-project-15.0.7/clang/include/clang/Driver/
H A DOptions.td2087 " expense of single-function patching performance">,