| commit | fd9f3beb0f3f1745c0eb71e4dbd29ed7c1d04ff6 | [log] [tgz] |
|---|---|---|
| author | Kazu Hirata <kazu@google.com> | Sat Nov 16 19:06:10 2024 -0800 |
| committer | GitHub <noreply@github.com> | Sat Nov 16 19:06:10 2024 -0800 |
| tree | a9ba380a62e1959c3479a56e4897deaf02e9189d | |
| parent | 8c7c8eaa1933d24c1eb869ba85469908547e3677 [diff] |
[memprof] Upgrade a unit test to Version 3 (#116516) I'm planning to remove MemProf Version 1, which is a maintenance burden because it uses a different set of struct fields in IndexedAllocationInfo and IndexedMemProfRecord compared to Version 2 and 3. (FWIW, Version 2 and 3 are much closer to each other.) Before we remove the old version, we need to upgrade test_memprof_merge to Version 3. Here are some remarks: - Without this patch, we call Writer.addMemProfFrame, which I don't think is correct. This way, we are adding IndexedMemProfRecord to Writer2 without any frame. I'm changing that to Writer2.addMemProfFrame. - This patch adds a call to getCallStackMapping. Version 2 and 3 require a map from call stack IDs to call stacks. - I'm calling makeRecordV2 instead of makeRecord to populate the struct fields used by Version 2 and 3. - Version 1 uses MemProfRecord::MemProfRecord (that is, a constructor) to convert IndexedMemProfRecord to MemProfRecord. Version 2 and 3 use MemProfRecord::toMemProfRecord, a member function, to do the same task.
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.