[llvm-commits] CVS: llvm/www/docs/CommandLine.html LangRef.html RegisterAllocatorInfo.txt WritingAnLLVMPass.html

[Misha Brukman]

Changes in directory llvm/www/docs:

CommandLine.html updated: 1.10 -> 1.11
LangRef.html updated: 1.25 -> 1.26
RegisterAllocatorInfo.txt updated: 1.3 -> 1.4
WritingAnLLVMPass.html updated: 1.13 -> 1.14

---
Log message:

The word `separate' only has one `e'.


---
Diffs of the changes:

Index: llvm/www/docs/CommandLine.html
diff -u llvm/www/docs/CommandLine.html:1.10 llvm/www/docs/CommandLine.html:1.11
--- llvm/www/docs/CommandLine.html:1.10	Sat Jun 21 16:45:56 2003
+++ llvm/www/docs/CommandLine.html	Mon Jul 14 12:20:40 2003
@@ -1109,7 +1109,7 @@
 
 <a name="cl::Prefix">The <b><tt>cl::Prefix</tt></b> modifier specifies that this
 option prefixes its value.  With 'Prefix' options, there is no equal sign that
-seperates the value from the option name specified.  This is useful for
+separates the value from the option name specified.  This is useful for
 processing odd arguments like '<tt>-lmalloc -L/usr/lib'</tt> in a linker tool.
 Here, the '<tt>l</tt>' and '<tt>L</tt>' options are normal string (list)
 options, that have the <a href="#cl::Prefix">cl::Prefix</a> modifier added to
@@ -1496,7 +1496,7 @@
 <address><a href="mailto:sabre at nondot.org">Chris Lattner</a></address>
 <!-- Created: Tue Jan 23 15:19:28 CST 2001 -->
 <!-- hhmts start -->
-Last modified: Sat Jun 21 16:45:29 CDT 2003
+Last modified: Mon Jul 14 12:12:15 CDT 2003
 <!-- hhmts end -->
 </font>
 </body></html>


Index: llvm/www/docs/LangRef.html
diff -u llvm/www/docs/LangRef.html:1.25 llvm/www/docs/LangRef.html:1.26
--- llvm/www/docs/LangRef.html:1.25	Wed Jun 18 16:30:51 2003
+++ llvm/www/docs/LangRef.html	Mon Jul 14 12:20:40 2003
@@ -366,7 +366,7 @@
   <returntype> (<parameter list>)
 </pre>
 
-Where '<tt><parameter list></tt>' is a comma seperated list of type
+Where '<tt><parameter list></tt>' is a comma-separated list of type
 specifiers.  Optionally, the parameter list may include a type <tt>...</tt>,
 which indicates that the function takes a variable number of arguments.  Note
 that there currently is no way to define a function in LLVM that takes a
@@ -1811,7 +1811,7 @@
 <address><a href="mailto:sabre at nondot.org">Chris Lattner</a></address>
 <!-- Created: Tue Jan 23 15:19:28 CST 2001 -->
 <!-- hhmts start -->
-Last modified: Wed Jun 18 16:29:55 CDT 2003
+Last modified: Mon Jul 14 12:12:22 CDT 2003
 <!-- hhmts end -->
 </font>
 </body></html>


Index: llvm/www/docs/RegisterAllocatorInfo.txt
diff -u llvm/www/docs/RegisterAllocatorInfo.txt:1.3 llvm/www/docs/RegisterAllocatorInfo.txt:1.4
--- llvm/www/docs/RegisterAllocatorInfo.txt:1.3	Tue Jan  8 10:31:28 2002
+++ llvm/www/docs/RegisterAllocatorInfo.txt	Mon Jul 14 12:20:40 2003
@@ -117,7 +117,7 @@
 6.2. Create Interference graphs
 -------------------------------
 Once live ranges are constructed, we can build interference graphs for each
-register class. Though each register class must have a seperate interference
+register class. Though each register class must have a separate interference
 graph, building all interference graphs is performed in one pass. Also, the
 adjacency list for each live range is built in this phase. Consequently, each
 register class has an interference graph (which is a bit matrix) and each
@@ -139,7 +139,7 @@
 
 6.4. Color all live ranges in each RegClass using graph coloring algo
 ---------------------------------------------------------------------
-Each register class is colored seperately using the graph coloring algo. When
+Each register class is colored separately using the graph coloring algo. When
 assigning colors, preference is given to live ranges with suggested colors
 so that if such a live range receives a color (i.e., not spilled), then
 we try to assign the color suggested for that live range. When this phase
@@ -157,7 +157,7 @@
 instance the first incoming int argument must be colored to %i0 on Sparc). If
 it didn't receive the correct color, we have to insert instruction to to move
 the value to the required register. Also, this phase produces the caller 
-saving code. All adition code produced is kept seperately until the last
+saving code. All adition code produced is kept separately until the last
 phase (see 6.6)
 
 


Index: llvm/www/docs/WritingAnLLVMPass.html
diff -u llvm/www/docs/WritingAnLLVMPass.html:1.13 llvm/www/docs/WritingAnLLVMPass.html:1.14
--- llvm/www/docs/WritingAnLLVMPass.html:1.13	Mon Jul 14 12:05:20 2003
+++ llvm/www/docs/WritingAnLLVMPass.html	Mon Jul 14 12:20:40 2003
@@ -1166,7 +1166,7 @@
 the semantics defined for passes above (specifically they cannot maintain state
 across invocations of their <tt>run*</tt> methods), a nice clean way to
 implement a multithreaded compiler would be for the <tt>PassManager</tt> class
-to create multiple instances of each pass object, and allow the seperate
+to create multiple instances of each pass object, and allow the separate
 instances to be hacking on different parts of the program at the same time.<p>
 
 This implementation would prevent each of the passes from having to implement
@@ -1223,6 +1223,6 @@
 <address><a href="mailto:sabre at nondot.org">Chris Lattner</a></address>
 <!-- Created: Tue Aug  6 15:00:33 CDT 2002 -->
 <!-- hhmts start -->
-Last modified: Mon Oct 21 14:52:55 CDT 2002
+Last modified: Mon Jul 14 12:12:53 CDT 2003
 <!-- hhmts end -->
 </font></body></html>