llvm/utils/FileCheck, branch release_28

Trailing whitespace.

2010-08-20T17:38:38Z

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@111656 91177308-0d34-0410-b5e6-96231b3b80d8

stringref-ize the MemoryBuffer::get apis. This requires

2010-04-05T22:42:30Z

a co-committed clang patch. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@100485 91177308-0d34-0410-b5e6-96231b3b80d8

FileCheck: Don't print "possibly intended match" line if it would match the

2010-03-19T18:07:43Z

"scanning from here" one. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@98971 91177308-0d34-0410-b5e6-96231b3b80d8

FileCheck: When looking for "possible matches", only compare against the prefix

2010-01-30T00:24:06Z

line. Turns out edit_distance can be slow if the string we are scanning for happens to be quite large. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@94860 91177308-0d34-0410-b5e6-96231b3b80d8

Minor code cleanup.

2010-01-29T21:57:46Z

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@94848 91177308-0d34-0410-b5e6-96231b3b80d8

Skip whitespace when looking for a potential intended match.

2010-01-29T21:55:16Z

Before: :94:1: note: possible intended match here movsd 4096(%rsi), %xmm0 ^ After: :94:2: note: possible intended match here movsd 4096(%rsi), %xmm0 ^ git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@94847 91177308-0d34-0410-b5e6-96231b3b80d8

Fix the position of the caret in the FileCheck error message.

2010-01-29T21:53:18Z

Before: test/CodeGen/X86/lsr-reuse.ll:52:34: error: expected string not found in input ; CHECK: movsd -2048(%rsi), %xmm0 ^ After: test/CodeGen/X86/lsr-reuse.ll:52:10: error: expected string not found in input ; CHECK: movsd -2048(%rsi), %xmm0 ^ git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@94846 91177308-0d34-0410-b5e6-96231b3b80d8

FileCheck: Switch "possible match" calculation to use StringRef::edit_distance.

2010-01-29T03:22:19Z

- Thanks Doug, who is obviously less lazy than me! git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@94795 91177308-0d34-0410-b5e6-96231b3b80d8

Fix FileCheck crash when fuzzy scanning starting at the end of the file.

2009-11-29T08:30:24Z

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@90065 91177308-0d34-0410-b5e6-96231b3b80d8

FileCheck, PR5239: Try to find the intended match on failures, but looking for a

2009-11-22T22:59:26Z

good nearby fuzzy match. Frequently the input is nearly correct, and just showing the user the a nearby sensible match is enough to diagnose the problem. - The "fuzzyness" is pretty simple and arbitrary, but worked on my three test cases. If you encounter problems, or places you think FileCheck should have guessed but didn't, please add test cases to PR5239. For example, previously FileCheck would report this: -- t.cpp:21:55: error: expected string not found in input // CHECK: define void @_Z2f25f2_s1([[i64_i64_ty]] %a0) ^ :19:30: note: scanning from here define void @_Z2f15f1_s1(%1) nounwind { ^ :19:30: note: with variable "i64_i64_ty" equal to "%0" -- and now it also reports this: -- :27:1: note: possible intended match here define void @_Z2f25f2_s1(%0) nounwind { ^ -- which makes it clear that the CHECK just has an extra ' %a0' in it, without having to check the input. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@89631 91177308-0d34-0410-b5e6-96231b3b80d8