From bc4a4565de8221ffc1856619590c23518b61f521 Mon Sep 17 00:00:00 2001 From: Daniel Dunbar Date: Fri, 19 Oct 2012 17:23:39 +0000 Subject: [PATCH] Fix some doc-os. llvm-svn: 166290 --- llvm/docs/TestingGuide.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/llvm/docs/TestingGuide.html b/llvm/docs/TestingGuide.html index fa3ff2b..ae2643f 100644 --- a/llvm/docs/TestingGuide.html +++ b/llvm/docs/TestingGuide.html @@ -802,8 +802,8 @@ define two separate CHECK lines that match on the same line. tool. To specify an expected fail, use the XFAIL keyword in the comments of the test program followed by a colon and one or more failure patterns. Each failure pattern can be either '*' (to specify fail everywhere), or a part of a - target triple (indicating the test should fail on that platfomr), or the name - of a configurable feature (for example, "loadable_module").. If there is a + target triple (indicating the test should fail on that platform), or the name + of a configurable feature (for example, "loadable_module"). If there is a match, the test is expected to fail. If not, the test is expected to succeed. To XFAIL everywhere just specify XFAIL: *. Here is an example of an XFAIL line:

-- 2.7.4