| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
without using regular expressions.
llvm-svn: 163371
|
|
|
|
|
|
|
|
| |
note/warning/error as a
string, pass it around as an enum.
llvm-svn: 142107
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
llvm-svn: 129192
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
via an out parm.
llvm-svn: 121958
|
|
|
|
|
|
| |
error_code &ec. And fix clients.
llvm-svn: 121379
|
|
|
|
| |
llvm-svn: 120298
|
|
|
|
|
|
|
|
| |
It can pass two tests below on Win32.
- Clang :: CodeGenCXX/dyncast.cpp
- LLVM :: CodeGen/ARM/globals.ll
llvm-svn: 119023
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
llvm-svn: 111656
|
|
|
|
|
|
| |
a co-committed clang patch.
llvm-svn: 100485
|
|
|
|
|
|
| |
"scanning from here" one.
llvm-svn: 98971
|
|
|
|
|
|
|
| |
line. Turns out edit_distance can be slow if the string we are scanning for
happens to be quite large.
llvm-svn: 94860
|
|
|
|
| |
llvm-svn: 94848
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
- Thanks Doug, who is obviously less lazy than me!
llvm-svn: 94795
|
|
|
|
| |
llvm-svn: 90065
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
^
<stdin>:19:30: note: scanning from here
define void @_Z2f15f1_s1(%1) nounwind {
^
<stdin>:19:30: note: with variable "i64_i64_ty" equal to "%0"
--
and now it also reports this:
--
<stdin>: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.
llvm-svn: 89631
|
|
|
|
|
|
|
| |
additional information about the current definitions of the variables used in
the string.
llvm-svn: 89628
|
|
|
|
|
|
|
| |
separate character.
- Chris, OK?
llvm-svn: 89626
|
|
|
|
|
|
|
|
|
|
| |
allows matching and remembering a string and then matching and
verifying that the string occurs later in the file.
Change X86/xor.ll to use this in some cases where the test was
checking for an arbitrary register allocation decision.
llvm-svn: 82891
|
|
|
|
|
|
| |
and makes the API more annoying. Add a Regex::getNumMatches() method.
llvm-svn: 82877
|
|
|
|
| |
llvm-svn: 82780
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
regex and matching it instead of trying to match chunks at a time.
Matching chunks at a time broke with check lines like
CHECK: foo {{.*}}bar
because the .* would eat the entire rest of the line and bar would
never match.
Now we just escape the fixed strings for the user, so that something
like:
CHECK: a() {{.*}}???
is matched as:
CHECK: {{a\(\) .*\?\?\?}}
transparently "under the covers".
llvm-svn: 82779
|
|
|
|
|
|
| |
perf win and is needed for future changes.
llvm-svn: 82777
|
|
|
|
| |
llvm-svn: 82758
|
|
|
|
| |
llvm-svn: 82754
|
|
|
|
|
|
|
|
| |
; CHECK: movl {{%e[a-z][xi]}}, %eax
or whatever.
llvm-svn: 82717
|
|
|
|
|
|
|
| |
CHECK strings, instead of canonicalizing the patterns directly. This allows
Pattern to just contain a StringRef instead of std::string.
llvm-svn: 82713
|
|
|
|
|
|
| |
the Pattern class.
llvm-svn: 82712
|
|
|
|
| |
llvm-svn: 82711
|
|
|
|
|
|
|
|
|
|
| |
; CHECK: foo
; CHECK-NOT: foo
; CHECK: bar
would always fail.
llvm-svn: 82424
|
|
|
|
| |
llvm-svn: 82410
|
|
|
|
| |
llvm-svn: 82408
|
|
|
|
| |
llvm-svn: 82407
|
|
|
|
|
|
| |
CHECK-NEXT is on.
llvm-svn: 79164
|
|
|
|
| |
llvm-svn: 79123
|
|
|
|
| |
llvm-svn: 79121
|
|
|
|
|
|
|
| |
trying to wrap strstr which is just too inconvenient. Make it
use a StringRef to avoid ".c_str()" calls.
llvm-svn: 79120
|
|
|
|
| |
llvm-svn: 79119
|
|
|
|
| |
llvm-svn: 77845
|
|
|
|
| |
llvm-svn: 75391
|
|
|
|
| |
llvm-svn: 75371
|
|
|
|
|
|
| |
away. This way you can write a space and it matches arbitrary spaces and tabs.
llvm-svn: 75370
|
|
|
|
| |
llvm-svn: 75076
|
|
llvm-svn: 75022
|