Conrad Poelman fc5bf040d8 fix check-clang-tools tests that fail due to Windows CRLF line endings ... Running check-clang-tools on Windows produces 5 test failures: Failed Tests (5): Clang Tools :: clang-apply-replacements/ClangRenameClassReplacements.cpp Clang Tools :: clang-apply-replacements/basic.cpp Clang Tools :: clang-apply-replacements/format.cpp Clang Tools :: clang-move/move-used-helper-decls.cpp Clang Tools :: clang-tidy/infrastructure/export-diagnostics.cpp Four of these failures are simply due to fixed character position offsets differing on Windows versus Linux, since Windows line endings take up two characters instead of one: clang-apply-replacements/ClangRenameClassReplacements.cpp runs clang-rename -offset=254 clang-apply-replacements/Inputs/basic/file[12].yaml specify e.g. FileOffset: 148 and Offset: 298 clang-apply-replacements/Inputs/format/{no,yes}.yaml specify e.g. FileOffset: 94 and Offset: 94 clang-tidy/infrastructure/export-diagnostics.cpp specifies e.g. CHECK-YAML-NEXT: FileOffset: 30 (The move-used-helper-decls.cpp failure seems more complex; clang-move adds a blank line after void HelperFun1() {} when clang-move/Inputs/helper_decls_test.cpp has LF line endings, but does not add a blank line when the input files has CRLF line endings. That difference in behavior seems like it may be an actual bug, but I have yet to track it down.) Differential Revision: https://reviews.llvm.org/D97625		2022-02-11 15:23:51 -07:00
..
.gitattributes	fix check-clang-tools tests that fail due to Windows CRLF line endings	2022-02-11 15:23:51 -07:00