Home
last modified time | relevance | path

Searched refs:sleds (Results 1 – 10 of 10) sorted by relevance

/external/swiftshader/third_party/llvm-7.0/llvm/test/tools/llvm-xray/X86/
Dextract-all-sledtypes.txt5 # clang++ -c all-sleds.cc -o all-sleds.o -fpic -std=c++11 -fxray-instrument
7 # RUN: llvm-xray extract %S/Inputs/all-sleds.o -s | FileCheck %s
/external/swiftshader/third_party/llvm-7.0/llvm/include/llvm/Support/
DTargetOpcodes.def162 /// Wraps a return instruction and its operands to enable adding nop sleds
163 /// either before or after the return. The nop sleds are useful for inserting
184 /// Wraps a tail call instruction and its operands to enable adding nop sleds
189 /// Wraps a logging call and its arguments with nop sleds. At runtime, this can
193 /// Wraps a typed logging call and its argument with nop sleds. At runtime, this
/external/swiftshader/third_party/llvm-7.0/llvm/include/llvm/XRay/
DInstrumentationMap.h97 const SledContainer &sleds() const { return Sleds; }; in sleds() function
/external/swiftshader/third_party/llvm-7.0/llvm/tools/llvm-xray/
Dxray-extract.cpp58 auto Sleds = Map.sleds(); in exportAsYAML()
/external/llvm/include/llvm/Target/
DTargetOpcodes.def149 /// Wraps a return instruction and its operands to enable adding nop sleds
150 /// either before or after the return. The nop sleds are useful for inserting
/external/swiftshader/third_party/llvm-7.0/llvm/docs/
DXRay.rst36 The compiler-inserted instrumentation points come in the form of nop-sleds in
248 // Patch the sleds, if we haven't yet.
/external/clang/include/clang/Driver/
DOptions.td787 HelpText<"Generate XRay instrumentation sleds on function entry and exit">;
/external/jline/src/src/test/resources/jline/example/
Denglish.gz
/external/cldr/tools/java/org/unicode/cldr/util/data/transforms/
Dinternal_raw_IPA.txt151095 sleds %28824 slɛdz
Dinternal_raw_IPA-old.txt180425 sleds %19122 slɛdz