[all-commits] [llvm/llvm-project] 4f047b: [DLCov] Origin-Tracking: Collect stack traces in ...

[Stephen Tozer via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 4f047bc5955c942d987844ff835239943f83c0cc
      https://github.com/llvm/llvm-project/commit/4f047bc5955c942d987844ff835239943f83c0cc
  Author: Stephen Tozer <stephen.tozer at sony.com>
  Date:   2025-07-03 (Thu, 03 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 (#146678)

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