diff options
author | Daniel Dunbar <daniel@zuster.org> | 2012-10-19 17:23:39 +0000 |
---|---|---|
committer | Daniel Dunbar <daniel@zuster.org> | 2012-10-19 17:23:39 +0000 |
commit | bc4a4565de8221ffc1856619590c23518b61f521 (patch) | |
tree | 008b33aebc026acbdb3474c49f9bcf402bb53124 /llvm/docs/TestingGuide.html | |
parent | 315bcbd145c37a696cce3b360f1cb77babeeff61 (diff) | |
download | bcm5719-llvm-bc4a4565de8221ffc1856619590c23518b61f521.tar.gz bcm5719-llvm-bc4a4565de8221ffc1856619590c23518b61f521.zip |
Fix some doc-os.
llvm-svn: 166290
Diffstat (limited to 'llvm/docs/TestingGuide.html')
-rw-r--r-- | llvm/docs/TestingGuide.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/docs/TestingGuide.html b/llvm/docs/TestingGuide.html index fa3ff2b0398..ae2643fe4e8 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 <tt>XFAIL: *</tt>. Here is an example of an <tt>XFAIL</tt> line:</p> |