diff options
| author | Mircea Trofin <mtrofin@google.com> | 2024-09-23 15:21:25 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-23 15:21:25 -0700 |
| commit | 783bac7ffb8f0d58d7381d90fcaa082eb0be1c1d (patch) | |
| tree | 93f998c44ffb7558c2f4f3c8057a9ffaa8c5514b /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp | |
| parent | 0a5edb4de408ae0405f85c3e4c6da5233f185f63 (diff) | |
[ctx_prof] Handle `select` and its `step` instrumentation (#109185)
The `step` instrumentation shouldn't be treated, during use, like an `increment`. The latter is treated as a BB ID. The step isn't that, it's more of a type of value profiling. We need to distinguish between the 2 when really looking for BB IDs (==increments), and handle appropriately `step`s. In particular, we need to know when to elide them because `select`s may get elided by function cloning, if the condition of the select is statically known.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions