Home
last modified time | relevance | path

Searched refs:recognizer (Results 1 – 18 of 18) sorted by relevance

/llvm-project-15.0.7/lldb/source/Target/
H A DStackFrameRecognizer.cpp51 StackFrameRecognizerSP recognizer, ConstString module, in AddRecognizer() argument
53 m_recognizers.push_front({(uint32_t)m_recognizers.size(), recognizer, false, in AddRecognizer()
59 StackFrameRecognizerSP recognizer, RegularExpressionSP module, in AddRecognizer() argument
61 m_recognizers.push_front({(uint32_t)m_recognizers.size(), recognizer, true, in AddRecognizer()
79 callback(entry.recognizer_id, entry.recognizer->GetName(), module_name, in ForEach()
83 callback(entry.recognizer_id, entry.recognizer->GetName(), in ForEach()
143 return entry.recognizer; in GetRecognizerForFrame()
150 auto recognizer = GetRecognizerForFrame(frame); in RecognizeFrame() local
151 if (!recognizer) in RecognizeFrame()
153 return recognizer->RecognizeFrame(frame); in RecognizeFrame()
/llvm-project-15.0.7/lldb/include/lldb/Target/
H A DStackFrameRecognizer.h103 void AddRecognizer(lldb::StackFrameRecognizerSP recognizer,
107 void AddRecognizer(lldb::StackFrameRecognizerSP recognizer,
128 lldb::StackFrameRecognizerSP recognizer; member
/llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/
H A Dhazard-pass-ordering.mir3 # Verify that the dedicated hazard recognizer pass is run after late peephole
5 # passes that are run before the final hazard recognizer.
H A Dhazard-inlineasm.mir5 # then the hazard recognizer should insert a s_nop in between them.
H A Dllvm.amdgcn.buffer.wbinvl1.vol.ll14 ; This used to crash in hazard recognizer
H A Dhazard-kill.mir5 # The hazard recognizer should mov another instruction into that slot (in this case the S_MOV_B32
H A Dhazard.mir63 # IMPLICIT_DEF/DBG_VALUE instructions should not prevent the hazard recognizer
H A Dllc-pipeline.ll133 ; GCN-O0-NEXT: Post RA hazard recognizer
389 ; GCN-O1-NEXT: Post RA hazard recognizer
679 ; GCN-O1-OPTS-NEXT: Post RA hazard recognizer
971 ; GCN-O2-NEXT: Post RA hazard recognizer
1276 ; GCN-O3-NEXT: Post RA hazard recognizer
H A Didot8u.ll279 ; 2nd MAD) to have the pattern-recognizer to kick in.
597 ; 2nd MAD) to have the pattern-recognizer to kick in.
915 ; to have the pattern-recognizer to kick in.
H A Didot4s.ll173 ; be sign_extended directly to i32; prevents the pattern recognizer to recognize this pattern.
H A Didot8s.ll324 ; pattern recognizer will kick in.
/llvm-project-15.0.7/lldb/test/Shell/Recognizer/
H A Dassert.test15 frame recognizer info 0
/llvm-project-15.0.7/llvm/test/CodeGen/Thumb2/
H A Dschedm7-hazard.ll5 ; This tests the cortex-m7 bank conflict hazard recognizer.
/llvm-project-15.0.7/lldb/source/Commands/
H A DCommandObjectFrame.cpp1107 auto recognizer = GetSelectedOrDummyTarget() in DoExecute() local
1113 if (recognizer) { in DoExecute()
1115 output_stream << recognizer->GetName(); in DoExecute()
H A DOptions.td400 let Command = "frame recognizer add" in {
403 Desc<"Name of the module or shared library that this recognizer applies "
407 Desc<"Name of the function that this recognizer applies to. "
411 Desc<"Give the name of a Python class to use for this frame recognizer.">;
415 Desc<"If true, only apply this recognizer to frames whose PC currently points to the "
416 "first instruction of the specified function. If false, the recognizer "
420 "be taken to make the recognizer operate correctly. Defaults to true.">;
/llvm-project-15.0.7/lldb/test/API/commands/frame/recognizer/
H A DTestFrameRecognizer.py11 import recognizer
/llvm-project-15.0.7/lldb/docs/use/
H A Dpython-reference.rst847 Adding a custom frame recognizer is done by implementing a Python class and
848 using the 'frame recognizer add' command. The Python class should have a
854 An example of a recognizer that retrieves the file descriptor values from libc
868 and then we can register this recognizer with ``frame recognizer add``.
869 It's important to restrict the recognizer to the libc library (which is
876 (lldb) frame recognizer add -l fd_recognizer.LibcFdRecognizer -n read -s libsystem_kernel.dylib
878 …opped at the beginning of the 'read' function in libc, we can view the recognizer arguments in 'fr…
/llvm-project-15.0.7/llvm/lib/Target/PowerPC/
H A DREADME_ALTIVEC.txt309 v4f32 or v4i32, probably because adding a dag pattern to the recognizer requires