Home
last modified time | relevance | path

Searched refs:LiveDebugValues (Results 1 – 25 of 35) sorted by relevance

12

/llvm-project-15.0.7/llvm/lib/CodeGen/LiveDebugValues/
H A DLiveDebugValues.cpp65 class LiveDebugValues : public MachineFunctionPass { class
69 LiveDebugValues();
70 ~LiveDebugValues() = default;
93 char LiveDebugValues::ID = 0;
95 char &llvm::LiveDebugValuesID = LiveDebugValues::ID;
97 INITIALIZE_PASS(LiveDebugValues, DEBUG_TYPE, "Live DEBUG_VALUE analysis", false,
101 LiveDebugValues::LiveDebugValues() : MachineFunctionPass(ID) { in LiveDebugValues() function in LiveDebugValues
108 bool LiveDebugValues::runOnMachineFunction(MachineFunction &MF) { in runOnMachineFunction()
H A DInstrRefBasedImpl.h30 namespace LiveDebugValues {
1161 using namespace LiveDebugValues; variable
/llvm-project-15.0.7/llvm/docs/
H A DInstrRefDebugInfo.md94 # `LiveDebugValues`
98 slots. This is performed in the [LiveDebugValues pass][`LiveDebugValues`], where
118 * Target hooks to be implemented to allow `LiveDebugValues` to follow values
126 instructions that are copy-like -- `LiveDebugValues` uses this to identify when
132 respectively. `LiveDebugValues` will track the movement of a value from / to
134 should have a `MachineMemoryOperand` attached, so that `LiveDebugValues` can
169 2 operand 0" recorded in the `MachineFunction`. In `LiveDebugValues`,
184 instruction, record no substitution -- `LiveDebugValues` will safely drop the
191 appearing to `LiveDebugValues`. Dealing with duplicated instructions is a
194 [LiveDebugValues]: SourceLevelDebugging.html#livedebugvalues-expansion-of-variable-locations
/llvm-project-15.0.7/llvm/utils/gn/secondary/llvm/lib/CodeGen/
H A DBUILD.gn76 "LiveDebugValues/InstrRefBasedImpl.cpp",
77 "LiveDebugValues/LiveDebugValues.cpp",
78 "LiveDebugValues/VarLocBasedImpl.cpp",
/llvm-project-15.0.7/llvm/lib/CodeGen/
H A DCMakeLists.txt234 LiveDebugValues/LiveDebugValues.cpp
235 LiveDebugValues/VarLocBasedImpl.cpp
236 LiveDebugValues/InstrRefBasedImpl.cpp
/llvm-project-15.0.7/llvm/test/DebugInfo/X86/
H A Dlive-debug-values.ll5 ; Generated from the source file LiveDebugValues.c:
27 ; with clang -g -O3 -emit-llvm -c LiveDebugValues.c -S -o live-debug-values.ll
41 ; ModuleID = 'LiveDebugValues.c'
116 !3 = !DIFile(filename: "LiveDebugValues.c", directory: "/home/vt/julia/test/tvvikram")
H A Dlive-debug-values-expr-conflict.ll5 ; LiveDebugValues should recognize that these are different locations, and not
H A Dlive-debug-values-remove-range.ll9 ; code-paths through LiveDebugValues. Any blocks with an incoming backedge need
/llvm-project-15.0.7/llvm/test/CodeGen/X86/
H A Ddebug-nodebug-crash.ll4 ; LiveDebugValues. This may lead to an assertion in the constructor for LexicalScope,
5 ; triggered by LiveDebugValues when another (debug) function is handled later.
/llvm-project-15.0.7/llvm/test/DebugInfo/MIR/InstrRef/
H A Dmemory-operand-tracking.mir6 # Test that memory operands of instructions are interpreted by LiveDebugValues:
76 ;; Overwrite the stack: LiveDebugValues should explicitly undef the stack
H A Dlivedebugvalues_recover_clobbers.mir4 ;; When using instruction referencing LiveDebugValues, when a register gets
8 ;; as this is purely a LiveDebugValues feature, and should work without the
H A Dwin32-chkctk-modifies-esp.mir6 ## in MIR when fed to LiveDebugValues. The matter of interest is that on win32,
12 ## LiveDebugValues, where it can be recovered after a clobber or moved around.
H A Dspill-slot-limits.mir11 # LiveDebugValues if an internal accounting limit is exceeded -- in this test,
H A Dfollow-spill-of-live-value.mir5 # Test that spills of live values to the stack are tracked by LiveDebugValues.
9 # Prior versions of LiveDebugValues only recognised spills to the stack if the
13 # Test that instr-ref LiveDebugValues is able to track r10's value from the
17 # is that LiveDebugValues can track the value, not where it puts it.
H A Dpick-vphi-in-shifting-loop.mir10 # This caused an infinite loop in a previous implementation of LiveDebugValues.
/llvm-project-15.0.7/llvm/test/DebugInfo/MIR/X86/
H A Dlive-debug-values-bad-transfer.mir5 # live-in on LiveDebugValues' first pass through the loop, but on the second it
22 # This doesn't occur under value-tracking LiveDebugValues though.
H A Dlivedebugvalues_load_in_loop.mir5 ; merges LiveDebugValues has a hard time picking which one the variable lives
6 ; in. Test two of these scenarios that old LiveDebugValues can't handle: when
H A Dlivedebugvalues_many_loop_heads.mir5 ; LiveDebugValues. The code structure is eight nested loops, with loop heads
8 ; important part is that it looks like nested loops to LiveDebugValues.
20 ; Value-tracking LiveDebugValues _must_ correctly identify each PHI value.
H A Dlive-debug-values.mir4 # Generated from the source file LiveDebugValues.c:
26 # with clang -g -O3 -c -emit-llvm LiveDebugValues.c -S -o live-debug-values.ll
112 !1 = !DIFile(filename: "LiveDebugValues.c", directory: "/home/vt/julia/test/tvvikram")
H A Dlive-debug-values-3preds.mir4 # Generated from the source file LiveDebugValues-3preds.c:
24 # with clang -g -O1 -c -emit-llvm LiveDebugValues-3preds.c -S -o live-debug-values-3preds.ll
109 !1 = !DIFile(filename: "LiveDebugValues-3preds.c", directory: "/home/vt/julia/test/tvvikram")
H A Dkill-entry-value-after-diamond-bbs.mir28 ## Final two lines: VarLoc LiveDebugValues cannot determine that the DBG_VALUEs
30 ## wheras instruction referencing LiveDebugValues can.
H A Dlive-debug-values-restore-collide.mir8 # Test that LiveDebugValues does not create any new variable locations.
H A Dlive-debug-values-fragments.mir5 # LiveDebugValues previously ignored fragments and only propagated the last
H A Ddbg-stack-value-range.mir7 # Since input locations at BB3 for same variable are different LiveDebugValues
/llvm-project-15.0.7/llvm/test/CodeGen/AArch64/
H A Dlive-debugvalues-sve.mir3 # FIXME: re-enable this run line when InstrRef LiveDebugValues is able to
7 # Test that the LiveDebugValues pass can correctly handle the address
16 # TODO: When LiveDebugValues pass supports reloads for AArch64, it should

12