From 7e11b725f4067fae2f53804b42317508f9409787 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Sat, 15 Aug 2009 15:40:48 +0000 Subject: [PATCH] add a stub for futher description of filecheck. llvm-svn: 79106 --- llvm/docs/TestingGuide.html | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/llvm/docs/TestingGuide.html b/llvm/docs/TestingGuide.html index 60fe18a8e5a6..7c2b42d25bbb 100644 --- a/llvm/docs/TestingGuide.html +++ b/llvm/docs/TestingGuide.html @@ -29,6 +29,7 @@
  • DejaGNU structure @@ -447,6 +448,26 @@ negatives).

    + +
    The FileCheck utility
    + + +
    + +

    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.

    + + + + +
    +
    Variables and substitutions