Tie the ordered/unordered predicate descriptions to their meaning wrt

to QNAN values.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@32272 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/LangRef.html b/docs/LangRef.html
index 1ca56a18a4ebd568c63ef8689b4f3cbbe3cdc8e9..64725a700fe6c6600697de7d2f08c2994fd54fbf 100644 (file)
--- a/docs/LangRef.html
+++ b/docs/LangRef.html
@@ -3152,6 +3152,8 @@ a value, just a keyword. The possibilities for the condition code are:
   <li><tt>uno</tt>: unordered (either nans)</li>
   <li><tt>true</tt>: no comparison, always returns true</li>
 </ol>
+<p>In the preceding, <i>ordered</i> means that neither operand is a QNAN while
+<i>unordered</i> means that either operand may be a QNAN.</p>
 <p>The <tt>val1</tt> and <tt>val2</tt> arguments must be of 
 <a href="#t_floating">floating point</a>, or a <a href="#t_packed">packed</a> 
 floating point type. They must have identical types.</p>