aboutsummaryrefslogtreecommitdiff
path: root/llvm/tools/llvm-objdump/llvm-objdump.cpp
diff options
context:
space:
mode:
authorPaul Kirth <paulkirth@google.com>2023-12-01 14:51:21 -0800
committerGitHub <noreply@github.com>2023-12-01 14:51:21 -0800
commitd22944d1cc54a3384a88d654d144ef62a693df16 (patch)
tree2b995115b2ae6bea9223ed203f494523fc56d84d /llvm/tools/llvm-objdump/llvm-objdump.cpp
parent5fe741f08e09a2eca276fc11d39240caa3d23cb2 (diff)
downloadllvm-d22944d1cc54a3384a88d654d144ef62a693df16.zip
llvm-d22944d1cc54a3384a88d654d144ef62a693df16.tar.gz
llvm-d22944d1cc54a3384a88d654d144ef62a693df16.tar.bz2
[cmake] Fix relative paths in prefix map (#74132)
When building debug version of LLVM with `LLVM_USE_RELATIVE_PATHS_IN_FILES=On` would cause source paths to be incorrect, and be prefixed by the build directory. This lead to source locations like the following: `../build/llvm/...`. Such paths do not exist, and existing debuggers can't adjust their search location because of the incorrect prefix. Ultimately, this happened because the relative path creation goes in the wrong direction, from source-dir to build-dir instead of from build-dir to source-dir. This patch swaps the directionality of the relative paths so that they get a proper prefix from the build directory. Given a build dir at `/build` and a project directory at `/llvm-project`, we get source locations like: `../llvm-project/llvm/lib/Transforms/...`, which a debugger can resolve once pointed to the correct project directory.
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions