Previously, the test didn't work because '\' characters appeared in the sed string, causing bogus escape characters to form in the substituted string literal. Switching to using '%/p' causes the path to be emitted with '/' characters instead, so that there are are no escaping issues.
Details
Details
- Reviewers
khemant aprantl echristo grimar kzhuravl - Commits
- rZORGa0711895c8c8: [test]Make test work on Windows
rZORG1c323fe48bba: [test]Make test work on Windows
rGa0711895c8c8: [test]Make test work on Windows
rG1c323fe48bba: [test]Make test work on Windows
rGce0da8ba82d0: [test]Make test work on Windows
rL360660: [test]Make test work on Windows
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
test/tools/llvm-objdump/X86/source-interleave-x86_64.ll | ||
---|---|---|
1 ↗ | (On Diff #199260) | Use single quotes? BTW, I'm curious what backslashes in single quotes do (in the expanded sed -e 's,SRC_COMPDIR,%p/Inputs,g') do on Windows... |
test/tools/llvm-objdump/X86/source-interleave-x86_64.ll | ||
---|---|---|
1 ↗ | (On Diff #199260) | I've not done this. Double-quotes work fine and are what were there before. |
test/tools/llvm-objdump/X86/source-interleave-x86_64.ll | ||
---|---|---|
1 ↗ | (On Diff #199260) | It's fine. I was asking because in POSIX sh the backslash in single quotes wouldn't cause issues. |