diff options
author | Kazu Hirata <kazu@google.com> | 2024-11-20 14:03:27 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-11-20 14:03:27 -0800 |
commit | ec5b729e651c48dfff67487e6bb24c218c35cda9 (patch) | |
tree | 422293621993d49ad9dd15b498cb8a54769c9f8d /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp | |
parent | 9be475af81ee36f1d360ad1d70b695c4b26c98fa (diff) | |
download | llvm-ec5b729e651c48dfff67487e6bb24c218c35cda9.zip llvm-ec5b729e651c48dfff67487e6bb24c218c35cda9.tar.gz llvm-ec5b729e651c48dfff67487e6bb24c218c35cda9.tar.bz2 |
[memprof] Upgrade a unit test to MemProf Version 3 (#117063)
This patch upgrades a unit test to MemProf Version 3 while removing
those bits that cannot be upgraded to Version 3.
The bits being removed expect instrprof_error::hash_mismatch from a
broken MemProf profile that references a frame that doesn't actually
exist. Now, Version 3 no longer issues
instrprof_error::hash_mismatch. Even if it still issued
instrprof_error::hash_mismatch, we would have a couple of hurdles:
- InstrProfWriter::addMemProfData will soon require all (or none) of
the fields (frames, call stacks, and records) be populated. That
is, it won't accept an instance of IndexedMemProfData with frames
missing.
- writeMemProfV3 asserts that every frame occurs at least once:
assert(MemProfData.Frames.size() == FrameHistogram.size());
This patch gives up on instrprof_error::hash_mismatch and tries to
trigger instrprof_error::unknown_function with the empty profile.
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions