aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Target/DirectX/DirectXTargetMachine.cpp
diff options
context:
space:
mode:
authorGrigory Pastukhov <99913765+grigorypas@users.noreply.github.com>2025-09-11 10:41:11 -0700
committerGitHub <noreply@github.com>2025-09-11 10:41:11 -0700
commit8c0f3b6e8f8db76e4ef47f38fb7b32ba9be1913b (patch)
treeaa08a69df5b2d8b4a7a0409c571b03c64803481c /llvm/lib/Target/DirectX/DirectXTargetMachine.cpp
parent299ba5dae13cfcad86e9c6f11b88178509d98e80 (diff)
downloadllvm-8c0f3b6e8f8db76e4ef47f38fb7b32ba9be1913b.zip
llvm-8c0f3b6e8f8db76e4ef47f38fb7b32ba9be1913b.tar.gz
llvm-8c0f3b6e8f8db76e4ef47f38fb7b32ba9be1913b.tar.bz2
[BOLT] Fix debug line emission for functions in multiple compilation units (#151230)
This patch fixes a bug in BOLT's debug line emission where functions that belong to multiple compilation units (such as inline functions in header files) were not handled correctly. Previously, BOLT incorrectly assumed that a binary function could belong to only one compilation unit, leading to incomplete or incorrect debug line information. ### **Problem** When a function appears in multiple compilation units (common scenarios include): * Template instantiated functions * Inline functions defined in header files included by multiple source files BOLT would only emit debug line information for one compilation unit, losing debug information for other CUs where the function was compiled. This resulted in incomplete debugging information and could cause debuggers to fail to set breakpoints or show incorrect source locations. ### **Root Cause** The issue was in BOLT's assumption that each binary function maps to exactly one compilation unit. However, when the same function (e.g., an inline function from a header) is compiled into multiple object files, it legitimately belongs to multiple CUs in the final binary.
Diffstat (limited to 'llvm/lib/Target/DirectX/DirectXTargetMachine.cpp')
0 files changed, 0 insertions, 0 deletions