diff options
| author | Adrian McCarthy <amccarth@google.com> | 2019-06-07 21:13:30 +0000 |
|---|---|---|
| committer | Adrian McCarthy <amccarth@google.com> | 2019-06-07 21:13:30 +0000 |
| commit | 4447d15aef08b10fddc2f3c5133f32cdbfb7f441 (patch) | |
| tree | 62c92ea49a582022aa259837d2cc5240bf76d844 /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | 13427e64de2b67e4ca42b2860c5d3ee50db0abfc (diff) | |
| download | llvm-4447d15aef08b10fddc2f3c5133f32cdbfb7f441.zip llvm-4447d15aef08b10fddc2f3c5133f32cdbfb7f441.tar.gz llvm-4447d15aef08b10fddc2f3c5133f32cdbfb7f441.tar.bz2 | |
Fix lit tests on Windows related to CR+LF
Problem discovered in the breakpoint lit test, but probably exists in others.
lldb-test splits lines on LF. Input files that are CR+LF separated (as is
common on Windows) then resulted in commands being sent to LLDB that ended
in CR, which confused the command interpreter.
This could be fixed at different levels:
1. Treat '\r' like a tab or space in the argument splitter.
2. Fix the line splitters (plural) in lldb-test.
3. Normalize the test files to LF only.
If we did only 3, I'd expect similar problems to recur, so this patch does
1 and 2. I may also do 3 in a separate patch later, but that's tricky
because I believe we have some input files that MUST use CR+LF.
Differential Revision: https://reviews.llvm.org/D62759
llvm-svn: 362844
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions