From: Chris Lattner Date: Sat, 15 Aug 2009 15:40:48 +0000 (+0000) Subject: add a stub for futher description of filecheck. X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=3d2de1d1754fc5844c19ffc1f2348c5a2f3751b4;p=oota-llvm.git add a stub for futher description of filecheck. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@79106 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html index 60fe18a8e5a..7c2b42d25bb 100644 --- a/docs/TestingGuide.html +++ b/docs/TestingGuide.html @@ -29,6 +29,7 @@
  • DejaGNU structure @@ -447,6 +448,26 @@ negatives).

    + + + + +
    + +

    A powerful feature of the RUN: lines is that it allows any arbitrary commands + to be executed as part of the test harness. While standard (portable) unix + tools like 'grep' work fine on run lines, as you see above, there are a lot + of caveats due to interaction with Tcl syntax, and we want to make that the + run lines are portable to a wide range of systems. Another major problem is + that grep is not very good at checking to verify that the output of a tools + contains a series of different output in a specific order. The FileCheck + tool was designed to help with these problems.

    + + + + +
    +