aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.h
diff options
context:
space:
mode:
authorMikołaj Piróg <mikolaj.maciej.pirog@intel.com>2025-10-08 18:13:32 +0200
committerGitHub <noreply@github.com>2025-10-08 18:13:32 +0200
commit91f4db77b07368b47d32eb4d384fda2b2e5c9617 (patch)
treec6da611035c2bc71e88f998b2f01ec56ba05cc65 /lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.h
parenta43fb2b11473a5f2025e016794243cba0c1e5ddd (diff)
downloadllvm-91f4db77b07368b47d32eb4d384fda2b2e5c9617.zip
llvm-91f4db77b07368b47d32eb4d384fda2b2e5c9617.tar.gz
llvm-91f4db77b07368b47d32eb4d384fda2b2e5c9617.tar.bz2
[SDAG] Use useDebugInstrRef instead of shouldUseDebugInstrRef (#160686)
`shouldUseDebugInstrRef` can return different value than `useDebugInstrRef`, since the first depends on opt level which can change. Inconsistent usage can lead to errors later. I believe that using `should...` instead of `use...` here is a result of a minor error during this: https://github.com/llvm/llvm-project/pull/94149/files#diff-8ec547e1244562c5837ed180dd9bed61b3cd960ef90bb6002ea2db41a67ed693 Notice how before the change `InstrRef` is assigned value from `should...` *before* the opt change. Now, it's done after -- opt change happens here: ```c bool SelectionDAGISelLegacy::runOnMachineFunction(MachineFunction &MF) { ... // Decide what flavour of variable location debug-info will be used, before // we change the optimisation level. MF.setUseDebugInstrRef(MF.shouldUseDebugInstrRef()); .... return Selector->runOnMachineFunction(MF); } ``` Then `runOnMachineFunction` uses `should...`, which after opt change may return different value than it did previously.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.h')
0 files changed, 0 insertions, 0 deletions