FileCheck: remove useless 'continue' at the end of a 'while(){}' loop.

llvm-svn: 168048

Support for [[@LINE]], [[@LINE+<offset>]], [[@LINE-<offset>]] expressions in
FileCheck.

llvm-svn: 167978

Clarify comment.

llvm-svn: 164371

FileCheck: Fix off-by-one bug that made CHECK-NOT: ignore the next character after the colon.

llvm-svn: 164165

Revert "Add -exact-match option to FileCheck to allow clients to do exact matches without using regular expressions."

Turns out I did not need it after all. If we find a use for it in the future, w

Revert "Add -exact-match option to FileCheck to allow clients to do exact matches without using regular expressions."

Turns out I did not need it after all. If we find a use for it in the future, we
can resurrect it.

llvm-svn: 163457

show more ...

Add -exact-match option to FileCheck to allow clients to do exact matches without using regular expressions.

llvm-svn: 163371

Make SMDiagnostic a little more sane. Instead of passing around note/warning/error as a
string, pass it around as an enum.

llvm-svn: 142107

Enhance llvm::SourceMgr to support diagnostic ranges, the same way clang does. Enhance
the X86 asmparser to produce ranges in the one case that was annoying me, for example:

test.s:10:15: error: in

Enhance llvm::SourceMgr to support diagnostic ranges, the same way clang does. Enhance
the X86 asmparser to produce ranges in the one case that was annoying me, for example:

test.s:10:15: error: invalid operand for instruction
movl 0(%rax), 0(%edx)
^~~~~~~

It should be straight-forward to enhance filecheck, tblgen, and/or the .ll parser to use
ranges where appropriate if someone is interested.

llvm-svn: 142106

show more ...

fix PR9629 - We were lowering regexes like a{{b|c}}d into ab|cd, which
is substantially different than a(b|c)d. Form the latter regex instead.
This found a few problems in the testsuite, which serve

fix PR9629 - We were lowering regexes like a{{b|c}}d into ab|cd, which
is substantially different than a(b|c)d. Form the latter regex instead.
This found a few problems in the testsuite, which serves as its test.

llvm-svn: 129196

show more ...

various cleanups, no functionality change.

llvm-svn: 129192

emit a specific error when the input file is empty. This fixes
an annoyance of mine when working on tests: if the input .ll file
is broken, opt outputs an error and generates an empty file. FileCh

emit a specific error when the input file is empty. This fixes
an annoyance of mine when working on tests: if the input .ll file
is broken, opt outputs an error and generates an empty file. FileCheck
then emits its "ooh I couldn't find the first CHECK line, scanning
from ..." which obfuscates the actual problem.

llvm-svn: 125193

show more ...

MemoryBuffer now return an error_code and returns a OwningPtr<MemoryBuffer> via an out parm.

llvm-svn: 121958

Support/MemoryBuffer: Replace all uses of std::string *ErrMsg with error_code &ec. And fix clients.

llvm-svn: 121379

Merge System into Support.

llvm-svn: 120298

FileCheck: Eliminate DOSish \r from input file.

It can pass two tests below on Win32.
- Clang :: CodeGenCXX/dyncast.cpp
- LLVM :: CodeGen/ARM/globals.ll

llvm-svn: 119023

Teach FileCheck to handle trailing CHECK-NOT patterns.

A CHECK-NOT pattern without a following CHECK pattern simply checks that the
pattern doesn't match before the end of the input file.

You can e

Teach FileCheck to handle trailing CHECK-NOT patterns.

A CHECK-NOT pattern without a following CHECK pattern simply checks that the
pattern doesn't match before the end of the input file.

You can even have only CHECK-NOT patterns to check that strings appear nowhere
in the input file.

llvm-svn: 116592

show more ...

Trailing whitespace.

llvm-svn: 111656

stringref-ize the MemoryBuffer::get apis. This requires
a co-committed clang patch.

llvm-svn: 100485

FileCheck: Don't print "possibly intended match" line if it would match the
"scanning from here" one.

llvm-svn: 98971

FileCheck: When looking for "possible matches", only compare against the prefix
line. Turns out edit_distance can be slow if the string we are scanning for
happens to be quite large.

llvm-svn: 94860

Minor code cleanup.

llvm-svn: 94848

Skip whitespace when looking for a potential intended match.
Before:

<stdin>:94:1: note: possible intended match here
movsd 4096(%rsi), %xmm0
^

After:
<stdin>:94:2: note: possible intended match h

Skip whitespace when looking for a potential intended match.
Before:

<stdin>:94:1: note: possible intended match here
movsd 4096(%rsi), %xmm0
^

After:
<stdin>:94:2: note: possible intended match here
movsd 4096(%rsi), %xmm0
^

llvm-svn: 94847

show more ...

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

test/CodeGen/X86/lsr-reuse.ll:52:34: error: expected string not found in input
; CHECK: movsd -2048(%rsi), %xmm0

Fix the position of the caret in the FileCheck error message.
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
^

llvm-svn: 94846

show more ...

FileCheck: Switch "possible match" calculation to use StringRef::edit_distance.
- Thanks Doug, who is obviously less lazy than me!

llvm-svn: 94795

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

llvm-svn: 90065