[llvm-commits] CVS: llvm/www/docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt 2001-05-18-ExceptionHandling.txt 2002-06-25-MegaPatchInfo.txt

Michael Brukman brukman at cs.uiuc.edu
Mon Aug 18 09:44:04 PDT 2003


Changes in directory llvm/www/docs/HistoricalNotes:

2001-02-09-AdveCommentsResponse.txt updated: 1.1.1.1 -> 1.2
2001-05-18-ExceptionHandling.txt updated: 1.1.1.1 -> 1.2
2002-06-25-MegaPatchInfo.txt updated: 1.1 -> 1.2

---
Log message:

Spell `necessary' correctly.


---
Diffs of the changes:

Index: llvm/www/docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt
diff -u llvm/www/docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt:1.1.1.1 llvm/www/docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt:1.2
--- llvm/www/docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt:1.1.1.1	Wed Jun  6 15:29:02 2001
+++ llvm/www/docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt	Mon Aug 18 09:42:50 2003
@@ -150,7 +150,7 @@
 Conditional move is effectly a special case of a predicated
 instruction... and I think that all predicated instructions can possibly
 be implemented later in LLVM.  It would significantly change things, and
-it doesn't seem to be very neccesary right now.  It would seem to
+it doesn't seem to be very necessary right now.  It would seem to
 complicate flow control analysis a LOT in the virtual machine.  I would
 tend to prefer that a predicated architecture like IA64 convert from a
 "basic block" representation to a predicated rep as part of it's dynamic


Index: llvm/www/docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt
diff -u llvm/www/docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt:1.1.1.1 llvm/www/docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt:1.2
--- llvm/www/docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt:1.1.1.1	Wed Jun  6 15:29:03 2001
+++ llvm/www/docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt	Mon Aug 18 09:42:50 2003
@@ -144,7 +144,7 @@
 2. A pointer to the dtor for the contained object
 3. The contained object itself
 
-Note that it is neccesary to maintain #1 & #2 in the exception object itself
+Note that it is necessary to maintain #1 & #2 in the exception object itself
 because objects without virtual function tables may be thrown (as in this 
 example).  Assuming this, TryHandler would look something like this:
 


Index: llvm/www/docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt
diff -u llvm/www/docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt:1.1 llvm/www/docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt:1.2
--- llvm/www/docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt:1.1	Tue Jun 25 11:09:22 2002
+++ llvm/www/docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt	Mon Aug 18 09:42:50 2003
@@ -43,7 +43,7 @@
 
   which is much more natural and what users expect.
 
-* Simplification of #include's: Before, it was neccesary for a .cpp file to
+* Simplification of #include's: Before, it was necessary for a .cpp file to
   include every .h file that it used.  Now things are batched a little bit more
   to make it easier to use.  Specifically, the include graph now includes these
   edges:





More information about the llvm-commits mailing list