summaryrefslogtreecommitdiffstats
path: root/llvm/docs/LangRef.html
diff options
context:
space:
mode:
authorReid Spencer <rspencer@reidspencer.com>2004-12-09 18:02:53 +0000
committerReid Spencer <rspencer@reidspencer.com>2004-12-09 18:02:53 +0000
commit8f08d805d43e7af2e3daf5dcf64c0ede6af4f9ad (patch)
treef8a1d141b44ba2f27b624db1721ed6bf2b086d0d /llvm/docs/LangRef.html
parent098fce4727bbb62a715b227f35997af7ce469c4e (diff)
downloadbcm5719-llvm-8f08d805d43e7af2e3daf5dcf64c0ede6af4f9ad.tar.gz
bcm5719-llvm-8f08d805d43e7af2e3daf5dcf64c0ede6af4f9ad.zip
Clean up some grammaro's.
llvm-svn: 18705
Diffstat (limited to 'llvm/docs/LangRef.html')
-rw-r--r--llvm/docs/LangRef.html21
1 files changed, 10 insertions, 11 deletions
diff --git a/llvm/docs/LangRef.html b/llvm/docs/LangRef.html
index 77c20c1c9db..ec18f23fbce 100644
--- a/llvm/docs/LangRef.html
+++ b/llvm/docs/LangRef.html
@@ -238,8 +238,8 @@ purposes:</p>
<li>Unnamed values are represented as an unsigned numeric value with a '%'
prefix. For example, %12, %2, %44.</li>
- <li>Constants, which are described in <a href="#constants">section about
- constants</a></li>
+ <li>Constants, which are described in a <a href="#constants">section about
+ constants</a>, below.</li>
</ol>
<p>LLVM requires that values start with a '%' sign for two reasons: Compilers
@@ -778,8 +778,7 @@ them all and their syntax.</p>
</div>
<!-- ======================================================================= -->
-<div class="doc_subsection"> <a name="simpleconstants">Simple Constants</a>
-</div>
+<div class="doc_subsection"><a name="simpleconstants">Simple Constants</a></div>
<div class="doc_text">
@@ -792,7 +791,7 @@ them all and their syntax.</p>
<dt><b>Integer constants</b></dt>
- <dd>Standard integers (such as '4') are constants of <a
+ <dd>Standard integers (such as '4') are constants of the <a
href="#t_integer">integer</a> type. Negative numbers may be used with signed
integer types.
</dd>
@@ -801,7 +800,7 @@ them all and their syntax.</p>
<dd>Floating point constants use standard decimal notation (e.g. 123.421),
exponential notation (e.g. 1.23421e+2), or a more precise hexadecimal
- notation. etc. Floating point constants have an optional hexadecimal
+ notation. Floating point constants have an optional hexadecimal
notation (see below). Floating point constants must have a <a
href="#t_floating">floating point</a> type. </dd>
@@ -816,11 +815,11 @@ them all and their syntax.</p>
of floating point constants. For example, the form '<tt>double
0x432ff973cafa8000</tt>' is equivalent to (but harder to read than) '<tt>double
4.5e+15</tt>'. The only time hexadecimal floating point constants are required
-(and the only time that they are generated by the disassembler) is when an FP
-constant has to be emitted that is not representable as a decimal floating point
-number exactly. For example, NaN's, infinities, and other special cases are
-represented in their IEEE hexadecimal format so that assembly and disassembly do
-not cause any bits to change in the constants.</p>
+(and the only time that they are generated by the disassembler) is when a
+floating point constant must be emitted but it cannot be represented as a
+decimal floating point number. For example, NaN's, infinities, and other
+special values are represented in their IEEE hexadecimal format so that
+assembly and disassembly do not cause any bits to change in the constants.</p>
</div>
OpenPOWER on IntegriCloud