From 721c201bd55ffb73cb2ba8d39e0570fa38c44e15 Mon Sep 17 00:00:00 2001 From: dim Date: Wed, 15 Aug 2012 19:34:23 +0000 Subject: Vendor import of llvm trunk r161861: http://llvm.org/svn/llvm-project/llvm/trunk@161861 --- docs/TestingGuide.html | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) (limited to 'docs/TestingGuide.html') diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html index 33ce793..804e929 100644 --- a/docs/TestingGuide.html +++ b/docs/TestingGuide.html @@ -4,7 +4,7 @@ LLVM Testing Infrastructure Guide - + @@ -626,6 +626,8 @@ define i8 @coerce_offset0(i32 %V, i32* %P) {
+ +

The CHECK: and CHECK-NOT: directives both take a pattern to match. For most uses of FileCheck, fixed string matching is perfectly sufficient. For some things, a more flexible form of matching is desired. To support this, FileCheck @@ -650,6 +652,8 @@ braces like you would in C. In the rare case that you want to match double braces explicitly from the input, you can use something ugly like {{[{][{]}} as your pattern.

+ +
@@ -659,6 +663,9 @@ braces explicitly from the input, you can use something ugly like
+ + +

It is often useful to match a pattern and then verify that it occurs again later in the file. For codegen tests, this can be useful to allow any register, but verify that that register is used consistently later. To do this, FileCheck @@ -690,6 +697,8 @@ that FileCheck is not actually line-oriented when it matches, this allows you to define two separate CHECK lines that match on the same line.

+ +
@@ -900,7 +909,7 @@ the Test Suite Makefile Guide.

John T. Criswell, Daniel Dunbar, Reid Spencer, and Tanya Lattner
The LLVM Compiler Infrastructure
- Last modified: $Date: 2012-04-18 10:02:25 +0200 (Wed, 18 Apr 2012) $ + Last modified: $Date: 2012-05-08 20:26:07 +0200 (Tue, 08 May 2012) $ -- cgit v1.1