[LLVMbugs] [Bug 5239] New: FileCheck should try to fuzzy match forward when checks fail
bugzilla-daemon at cs.uiuc.edu
bugzilla-daemon at cs.uiuc.edu
Sun Oct 18 18:48:34 PDT 2009
http://llvm.org/bugs/show_bug.cgi?id=5239
Summary: FileCheck should try to fuzzy match forward when checks
fail
Product: tools
Version: trunk
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: gccas
AssignedTo: unassignedbugs at nondot.org
ReportedBy: daniel at zuster.org
CC: llvmbugs at cs.uiuc.edu
Consider this log taken from a buildbot:
--
******************** TEST 'Clang::CodeGenCXX/references.cpp' FAILED
********************Script:
--
/Users/buildslave/zorg/smooshlab/slaves/clang/build.clang-i386-darwin9/llvm/Debug/bin/clang-cc
-verify -emit-llvm -o -
/Users/buildslave/zorg/smooshlab/slaves/clang/build.clang-i386-darwin9/llvm/tools/clang/test/CodeGenCXX/references.cpp
| FileCheck
/Users/buildslave/zorg/smooshlab/slaves/clang/build.clang-i386-darwin9/llvm/tools/clang/test/CodeGenCXX/references.cpp
--
Exit Code: 1
Command Output (stdout):
--
--
Command Output (stderr):
--
/Users/buildslave/zorg/smooshlab/slaves/clang/build.clang-i386-darwin9/llvm/tools/clang/test/CodeGenCXX/references.cpp:124:34:
error: expected string not found in input
// CHECK: call void @_ZN1T1B1fEv
^
<stdin>:245:24: note: scanning from here
call void @_ZN1T1BC1Ev(%struct.A* %tmp)
^
--
********************
--
The failure is probably something about the mangling being different on the
platform in question. It would be nice if when there is a check failure,
FileCheck would scan forward "fuzzily" trying to find the most likely match.
For example, if the next line in the log was 'call void @_ZN1T1B$@^@' I would
like to see an additional:
--
<stdin>:246:1: note: found likely match here:
call void @_ZN1T1B$@^@
^
--
The "fuzzyness" could be something like minimum edit distance within the next
1k characters, or so.
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list