[all-commits] [llvm/llvm-project] 1320d5: [DLCov] Origin-Tracking: Collect stack traces in D...

[Stephen Tozer via All-commits]

  Branch: refs/heads/users/SLTozer/dl-coverage-origin-symbolize
  Home:   https://github.com/llvm/llvm-project
  Commit: 1320d5fb3a25f5ef73e9d2bf31b362c4e2d74848
      https://github.com/llvm/llvm-project/commit/1320d5fb3a25f5ef73e9d2bf31b362c4e2d74848
  Author: Stephen Tozer <stephen.tozer at sony.com>
  Date:   2025-07-02 (Wed, 02 Jul 2025)

  Changed paths:
    M llvm/include/llvm/IR/DebugLoc.h
    M llvm/include/llvm/IR/Instruction.h
    M llvm/lib/CodeGen/BranchFolding.cpp
    M llvm/lib/IR/DebugLoc.cpp

  Log Message:
  -----------
  [DLCov] Origin-Tracking: Collect stack traces in DebugLoc (#143592)

This patch is part of a series that adds origin-tracking to the debugify
source location coverage checks, allowing us to report symbolized stack
traces of the point where missing source locations appear.

This patch adds the logic for collecting stack traces in `DebugLoc`
instances. We do not symbolize the stack traces in this patch - that
only happens when we decide to actually print them, which will be the
responsibility of debugify. The collection happens in the constructor of
a `DebugLoc` that has neither a valid location nor an annotation; we
also collect an extra stack trace every time we call `setDebugLoc`, as
sometimes the more interesting point is not where the `DebugLoc` was
constructed, but where it was applied to an instruction. This takes the
form of a `getCopied()` method on `DebugLoc`, which is the identity
function in normal builds, but adds an extra stack trace in
origin-tracking builds.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications