diff options
| author | Kazu Hirata <kazu@google.com> | 2024-11-12 21:37:29 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-12 21:37:29 -0800 |
| commit | 95554cbd7717e7d1925f475540a70603bcb3a224 (patch) | |
| tree | 375cc0b0014b1292ad6378b50601ab8f6d96e882 /clang/unittests/Frontend/CompilerInvocationTest.cpp | |
| parent | 5911fbb39d615b39f1bf6fd732503ab433de5f27 (diff) | |
| download | llvm-95554cbd7717e7d1925f475540a70603bcb3a224.zip llvm-95554cbd7717e7d1925f475540a70603bcb3a224.tar.gz llvm-95554cbd7717e7d1925f475540a70603bcb3a224.tar.bz2 | |
[memprof] Teach extractCallsFromIR to recognize heap allocation functions (#115938)
This patch teaches extractCallsFromIR to recognize heap allocation
functions. Specifically, when we encounter a callee that is known to
be a heap allocation function like "new", we set the callee GUID to 0.
Note that I am planning to do the same for the caller-callee pairs
extracted from the profile. That is, when I encounter a frame that
does not have a callee, we assume that the frame is calling some heap
allocation function with GUID 0.
Technically, I'm not recognizing enough functions in this patch.
TCMalloc is known to drop certain frames in the call stack immediately
above new. This patch is meant to lay the groundwork, setting up
GetTLI, plumbing it to extractCallsFromIR, and adjusting the unit
tests. I'll address remaining issues in subsequent patches.
Diffstat (limited to 'clang/unittests/Frontend/CompilerInvocationTest.cpp')
0 files changed, 0 insertions, 0 deletions