diff options
author | Kazu Hirata <kazu@google.com> | 2024-11-26 23:48:03 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-11-26 23:48:03 -0800 |
commit | c00e53208db638c35499fc80b555f8e14baa35f0 (patch) | |
tree | 6afae1dd49aec877b23bbd36e60d40c3ec8c0497 /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp | |
parent | 50dfb0772b3995c6e5543600b2813f56d0736442 (diff) | |
download | llvm-c00e53208db638c35499fc80b555f8e14baa35f0.zip llvm-c00e53208db638c35499fc80b555f8e14baa35f0.tar.gz llvm-c00e53208db638c35499fc80b555f8e14baa35f0.tar.bz2 |
[memprof] Add YAML-based deserialization for MemProf profile (#117829)
This patch adds YAML-based deserialization for MemProf profile.
It's been painful to write tests for MemProf passes because we do not
have a text format for the MemProf profile. We would write a test
case in C++, run it for a binary MemProf profile, and then finally run
a test written in LLVM IR with the binary profile.
This patch paves the way toward YAML-based MemProf profile.
Specifically, it adds new class YAMLMemProfReader derived from
MemProfReader. For now, it only adds a function to parse StringRef
pointing to YAML data. Subseqeunt patches will wire it to
llvm-profdata and read from a file.
The field names are based on various printYAML functions in MemProf.h.
I'm not aiming for compatibility with the format used in printYAML,
but I don't see a point in changing the field names.
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.cpp')
0 files changed, 0 insertions, 0 deletions