Google Git
Sign in
llvm / llvm-project / 79e93178934eb93acf252de093c263f4db9eb8b7
commit79e93178934eb93acf252de093c263f4db9eb8b7[log] [tgz]
authorStephen Tozer <stephen.tozer@sony.com>Wed Sep 10 13:30:21 2025 +0100
committerGitHub <noreply@github.com>Wed Sep 10 13:30:21 2025 +0100
tree86c1380e85828ad6e38474135b6ea87b000716ee
parenta76b02ddebf365c578f4902bba6946e8c2bfb1fc [diff]
[DebugInfo] When merging locations prefer unannotated empty locs (#157707)

When merging DILocations, we prefer to use DebugLoc::getMergedLocation
when possible to better preserve DebugLoc coverage tracking information
through transformations (as conversion to DILocations drops all coverage
tracking data). Currently, DebugLoc::getMergedLocation checks to see if
either DebugLoc is empty and returns it directly if so, to propagate
that DebugLoc's coverage tracking data to the merged location; however,
it only checks whether either location is valid, not whether they are
annotated.

This is significant because an annotated location is not a bug, while an
empty unannotated location may be one; therefore, we check to see if
either location is unannotated, and prefer to return that location if it
exists rather than an annotated one.

This change is NFC outside of DebugLoc coverage tracking builds.
1 file changed
tree: 86c1380e85828ad6e38474135b6ea87b000716ee
  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.