diff options
| author | Walter Erquinigo <wallace@fb.com> | 2020-10-02 14:32:22 -0700 |
|---|---|---|
| committer | Walter Erquinigo <wallace@fb.com> | 2020-10-12 12:08:18 -0700 |
| commit | 26d861cbbd5f40182b3b7f0ac7ed0e58e0e8feaa (patch) | |
| tree | 2daa0ee0828025a78d3b2f6b482a3c8c50275691 /llvm/lib/Transforms/Utils/SimplifyIndVar.cpp | |
| parent | 388d373294e1f7386e1bc14338bd985189f47604 (diff) | |
| download | llvm-26d861cbbd5f40182b3b7f0ac7ed0e58e0e8feaa.zip llvm-26d861cbbd5f40182b3b7f0ac7ed0e58e0e8feaa.tar.gz llvm-26d861cbbd5f40182b3b7f0ac7ed0e58e0e8feaa.tar.bz2 | |
[trace] Scaffold "thread trace dump instructions"
Depends on D88841
As per the discussion in the RFC, we'll implement both
thread trace dump [instructions | functions]
This is the first step in implementing the "instructions" dumping command.
It includes:
- A minimal ProcessTrace plugin for representing processes from a trace file. I noticed that it was a required step to mimic how core-based processes are initialized, e.g. ProcessElfCore and ProcessMinidump. I haven't had the need to create ThreadTrace yet, though. So far HistoryThread seems good enough.
- The command handling itself in CommandObjectThread, which outputs a placeholder text instead of the actual instructions. I'll do that part in the next diff.
- Tests
{F13132325}
Differential Revision: https://reviews.llvm.org/D88769
Diffstat (limited to 'llvm/lib/Transforms/Utils/SimplifyIndVar.cpp')
0 files changed, 0 insertions, 0 deletions