The file path we print in the message header is then used by Visual Studio to fill Error List so that a user can click on an item and jump to the mentioned location. If we use only a name part for that, Visual Studio might be unable to find the file or, even worse, show a wrong one.
Details
Details
- Reviewers
ruiu MaskRay chrisjackson grimar • espindola - Commits
- rGb65016ddac32: [ELF] For VS-style diagnostics, prefer printing full paths in the header.
rL368409: [ELF] For VS-style diagnostics, prefer printing full paths in the header.
rLLD368409: [ELF] For VS-style diagnostics, prefer printing full paths in the header.
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
Generally looking good, but do these tests pass on Windows on which a path separator is \? It seems like you hardcoded / as a path separator in the tests.
Comment Actions
LGTM
I confirmed that these tests are not affected by the actual path on a machine running the tests. I missed the part that you added .line directive in this patch. Thank you for doing this.