From cbb70ce070d220642b038ea101d9c0f9fbf860d6 Mon Sep 17 00:00:00 2001
From: dim <dim@FreeBSD.org>
Date: Sun, 20 Feb 2011 12:57:14 +0000
Subject: Vendor import of llvm trunk r126079:
 http://llvm.org/svn/llvm-project/llvm/trunk@126079

---
 docs/CommandGuide/FileCheck.pod | 4 ++--
 docs/CommandGuide/index.html    | 2 +-
 docs/CommandGuide/llc.pod       | 8 ++++++++
 docs/CommandGuide/lli.pod       | 9 ++++++---
 4 files changed, 17 insertions(+), 6 deletions(-)

(limited to 'docs/CommandGuide')

diff --git a/docs/CommandGuide/FileCheck.pod b/docs/CommandGuide/FileCheck.pod
index 433979a..3ccaa63 100644
--- a/docs/CommandGuide/FileCheck.pod
+++ b/docs/CommandGuide/FileCheck.pod
@@ -133,7 +133,7 @@ both 32-bit and 64-bit code generation.
 =head2 The "CHECK-NEXT:" directive
 
 Sometimes you want to match lines and would like to verify that matches
-happen on exactly consequtive lines with no other lines in between them.  In
+happen on exactly consecutive lines with no other lines in between them.  In
 this case, you can use CHECK: and CHECK-NEXT: directives to specify this.  If
 you specified a custom check prefix, just use "<PREFIX>-NEXT:".  For
 example, something like this works as you'd expect:
@@ -165,7 +165,7 @@ directive in a file.
 =head2 The "CHECK-NOT:" directive
 
 The CHECK-NOT: directive is used to verify that a string doesn't occur
-between two matches (or the first match and the beginning of the file).  For
+between two matches (or before the first match, or after the last match).  For
 example, to verify that a load is removed by a transformation, a test like this
 can be used:
 
diff --git a/docs/CommandGuide/index.html b/docs/CommandGuide/index.html
index 67f0cfc..3c1a9f9 100644
--- a/docs/CommandGuide/index.html
+++ b/docs/CommandGuide/index.html
@@ -151,7 +151,7 @@ options) arguments to the tool you are interested in.</p>
   src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
 
   <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2010-09-08 01:32:02 +0200 (Wed, 08 Sep 2010) $
+  Last modified: $Date: 2010-09-08 01:10:21 +0200 (Wed, 08 Sep 2010) $
 </address>
 
 </body>
diff --git a/docs/CommandGuide/llc.pod b/docs/CommandGuide/llc.pod
index ac24aab..eb26ec0 100644
--- a/docs/CommandGuide/llc.pod
+++ b/docs/CommandGuide/llc.pod
@@ -84,6 +84,14 @@ Disable optimizations that may produce excess precision for floating point.
 Note that this option can dramatically slow down code on some systems
 (e.g. X86).
 
+=item B<--enable-no-infs-fp-math>
+
+Enable optimizations that assume no Inf values.
+
+=item B<--enable-no-nans-fp-math>
+
+Enable optimizations that assume no NAN values.
+
 =item B<--enable-unsafe-fp-math>
 
 Enable optimizations that make unsafe assumptions about IEEE math (e.g. that
diff --git a/docs/CommandGuide/lli.pod b/docs/CommandGuide/lli.pod
index d368bec..52a2721 100644
--- a/docs/CommandGuide/lli.pod
+++ b/docs/CommandGuide/lli.pod
@@ -102,10 +102,13 @@ B<llvm-as E<lt> /dev/null | llc -march=xyz -mattr=help>
 
 Disable optimizations that may increase floating point precision.
 
-=item B<-enable-finite-only-fp-math>
+=item B<-enable-no-infs-fp-math>
 
-Enable optimizations that assumes only finite floating point math. That is,
-there is no NAN or Inf values.
+Enable optimizations that assume no Inf values.
+
+=item B<-enable-no-nans-fp-math>
+
+Enable optimizations that assume no NAN values.
 
 =item B<-enable-unsafe-fp-math>
 
-- 
cgit v1.1