Google Git
Sign in
llvm/llvm-project/7cfb9bcbe3a02e9de8cd4e22efa4940b40d49d21
commit
7cfb9bcbe3a02e9de8cd4e22efa4940b40d49d21
[log]
author
Amir Ayupov <aaupov@fb.com>
Fri May 15 00:17:30 2026 -0700
committer
GitHub <noreply@github.com>
Fri May 15 00:17:30 2026 -0700
tree
8a6119e911dfb82ffacfee9a9c2326eb6fb195f4
parent
bef7245d912795a3eb6db326165e9776eebe8695 [diff]
[BOLT] Allow name matching stale profiles with infer-stale-profile (#165493)

Exact name matching of a YAML profile to a BinaryFunction is
conditional on `profileMatches`:

https://github.com/llvm/llvm-project/blob/5c7854c8ed1998650af6f01761df385712f5295a/bolt/lib/Profile/YAMLProfileReader.cpp#L419-L421

With stale profile, both function hash and block count can mismatch, so
exact name matching fails. After it, we run other function matching
plus fallback exact-name-matching of unused profiles:


https://github.com/llvm/llvm-project/blob/a7e4e2521e77f638e6740059109725c9a4d89453/bolt/lib/Profile/YAMLProfileReader.cpp#L833-L843

In effect, for stale profile, both with and without stale matching, we
ignore the strong signal of exactly matching function name, run a batch
of looser checks, and finally assign the profile in the fallback.

Change to record exact-name-matching profiles if stale matching is used
to 1) avoid running other checks, 2) use such pairs as roots for pseudo
probe matching. Also make fallback matching an explicit step.

Test Plan: updated reader-stale-yaml.test
3 files changed
tree: 8a6119e911dfb82ffacfee9a9c2326eb6fb195f4
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cross-project-tests/
  9. flang/
  10. flang-rt/
  11. libc/
  12. libclc/
  13. libcxx/
  14. libcxxabi/
  15. libsycl/
  16. libunwind/
  17. lld/
  18. lldb/
  19. llvm/
  20. llvm-libgcc/
  21. mlir/
  22. offload/
  23. openmp/
  24. orc-rt/
  25. polly/
  26. runtimes/
  27. third-party/
  28. utils/
  29. .clang-format
  30. .clang-format-ignore
  31. .clang-tidy
  32. .git-blame-ignore-revs
  33. .gitattributes
  34. .gitignore
  35. .mailmap
  36. CODE_OF_CONDUCT.md
  37. CONTRIBUTING.md
  38. LICENSE.TXT
  39. pyproject.toml
  40. README.md
  41. SECURITY.md
README.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

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.

Getting the Source Code and Building LLVM

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.

Getting in touch

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.