aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/SwiftErrorValueTracking.cpp
diff options
context:
space:
mode:
authorIgor Kudrin <ikudrin@accesssoftek.com>2019-05-24 04:46:22 +0000
committerIgor Kudrin <ikudrin@accesssoftek.com>2019-05-24 04:46:22 +0000
commit0de4e935bb591b8c9ee41a9acbb5cda02838d8a6 (patch)
treec09ae9e3168beffad7148356958849241e8401ac /llvm/lib/CodeGen/SwiftErrorValueTracking.cpp
parent0ee23c958bbcf6955568d5287d1495f485426800 (diff)
downloadllvm-0de4e935bb591b8c9ee41a9acbb5cda02838d8a6.zip
llvm-0de4e935bb591b8c9ee41a9acbb5cda02838d8a6.tar.gz
llvm-0de4e935bb591b8c9ee41a9acbb5cda02838d8a6.tar.bz2
Do not resolve directory junctions for `-fdiagnostics-absolute-paths` on Windows.
If the source file path contains directory junctions, and we resolve them when printing diagnostic messages, these paths look independent for an IDE. For example, both Visual Studio and Visual Studio Code open separate editors for such paths, which is not only inconvenient but might even result in losing changes made in one of them. Differential Revision: https://reviews.llvm.org/D59415 llvm-svn: 361598
Diffstat (limited to 'llvm/lib/CodeGen/SwiftErrorValueTracking.cpp')
0 files changed, 0 insertions, 0 deletions