diff options
| author | Med Ismail Bennani <ismail@bennani.ma> | 2025-11-11 12:18:45 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-11-11 20:18:45 +0000 |
| commit | 1e467e44851a9da96c16c0dcd16725f996e6abf7 (patch) | |
| tree | abdc4638385ff1f196cf85ba8d8f093f982942e2 /llvm/test/CodeGen/AMDGPU/remat-fp64-constants.ll | |
| parent | 75ef0be0c3b6b0313d541b2af673ee4bb091572b (diff) | |
| download | llvm-main.zip llvm-main.tar.gz llvm-main.tar.bz2 | |
This patch extends ScriptedFrame to work with real (non-scripted)
threads,
enabling frame providers to synthesize frames for native processes.
Previously, ScriptedFrame only worked within
ScriptedProcess/ScriptedThread
contexts. This patch decouples ScriptedFrame from ScriptedThread,
allowing
users to augment or replace stack frames in real debugging sessions for
use
cases like custom calling conventions, reconstructing corrupted frames
from
core files, or adding diagnostic frames.
Key changes:
- ScriptedFrame::Create() now accepts ThreadSP instead of requiring
ScriptedThread, extracting architecture from the target triple rather
than ScriptedProcess.arch
- Added SBTarget::RegisterScriptedFrameProvider() and
ClearScriptedFrameProvider() APIs, with Target storing a
SyntheticFrameProviderDescriptor template for new threads
- Added "target frame-provider register/clear" commands for CLI access
- Thread class gains LoadScriptedFrameProvider(),
ClearScriptedFrameProvider(),
and GetFrameProvider() methods for per-thread frame provider management
- New SyntheticStackFrameList overrides FetchFramesUpTo() to lazily
provide
frames from either the frame provider or the real stack
This enables practical use of the SyntheticFrameProvider infrastructure
in
real debugging workflows.
rdar://161834688
Signed-off-by: Med Ismail Bennani <ismail@bennani.ma>
Signed-off-by: Med Ismail Bennani <ismail@bennani.ma>
Diffstat (limited to 'llvm/test/CodeGen/AMDGPU/remat-fp64-constants.ll')
0 files changed, 0 insertions, 0 deletions