From 5560c9d49ccae132cabf1155f18aa0480dce3eda Mon Sep 17 00:00:00 2001 From: Misha Brukman Date: Mon, 18 Aug 2003 14:43:39 +0000 Subject: Spell `necessary' correctly. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7944 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/AliasAnalysis.html | 2 +- docs/CodingStandards.html | 4 ++-- docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt | 2 +- docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt | 2 +- docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt | 2 +- docs/OpenProjects.html | 2 +- docs/ProgrammersManual.html | 8 ++++---- docs/WritingAnLLVMPass.html | 4 ++-- include/Support/DOTGraphTraits.h | 2 +- include/Support/PostOrderIterator.h | 2 +- include/llvm/ADT/PostOrderIterator.h | 2 +- include/llvm/Analysis/AliasSetTracker.h | 2 +- include/llvm/Analysis/Dominators.h | 2 +- include/llvm/Analysis/IntervalIterator.h | 2 +- include/llvm/Bytecode/Primitives.h | 2 +- include/llvm/Pass.h | 8 ++++---- include/llvm/Support/DOTGraphTraits.h | 2 +- include/llvm/Support/InstVisitor.h | 2 +- include/llvm/Target/TargetData.h | 2 +- lib/Analysis/LoadValueNumbering.cpp | 2 +- lib/AsmParser/llvmAsmParser.y | 2 +- lib/Bytecode/Reader/Reader.cpp | 2 +- lib/CodeGen/RegAllocSimple.cpp | 2 +- lib/ExecutionEngine/Interpreter/ExternalFunctions.cpp | 2 +- lib/Target/CBackend/CBackend.cpp | 4 ++-- lib/Target/CBackend/Writer.cpp | 4 ++-- lib/Target/SparcV9/SparcV9AsmPrinter.cpp | 6 +++--- lib/Target/TargetData.cpp | 4 ++-- lib/Target/X86/FloatingPoint.cpp | 2 +- lib/Target/X86/X86CodeEmitter.cpp | 2 +- lib/Target/X86/X86FloatingPoint.cpp | 2 +- lib/Target/X86/X86RegisterInfo.cpp | 2 +- lib/Transforms/ExprTypeConvert.cpp | 4 ++-- lib/Transforms/IPO/RaiseAllocations.cpp | 2 +- lib/Transforms/Scalar/ADCE.cpp | 2 +- lib/Transforms/Scalar/Reassociate.cpp | 2 +- lib/Transforms/Scalar/SCCP.cpp | 2 +- lib/Transforms/Utils/BasicBlockUtils.cpp | 2 +- lib/Transforms/Utils/LoopSimplify.cpp | 2 +- lib/Transforms/Utils/LowerAllocations.cpp | 2 +- lib/Transforms/Utils/PromoteMemoryToRegister.cpp | 2 +- lib/VMCore/Dominators.cpp | 2 +- lib/VMCore/Pass.cpp | 2 +- lib/VMCore/Verifier.cpp | 2 +- support/tools/TableGen/FileParser.y | 2 +- test/CFrontend/2002-02-13-ReloadProblem.c | 2 +- tools/bugpoint/CrashDebugger.cpp | 4 ++-- tools/bugpoint/ListReducer.h | 2 +- tools/extract/README.txt | 2 +- utils/TableGen/FileParser.y | 2 +- 50 files changed, 65 insertions(+), 65 deletions(-) diff --git a/docs/AliasAnalysis.html b/docs/AliasAnalysis.html index d29ec927fe..51a80ef09c 100644 --- a/docs/AliasAnalysis.html +++ b/docs/AliasAnalysis.html @@ -68,7 +68,7 @@ this class exposes Mod/Ref information from those implementations which can provide it, allowing for powerful analyses and transformations to work well together.

-This document contains information neccesary to successfully implement this +This document contains information necessary to successfully implement this interface, use it, and to test both sides. It also explains some of the finer points about what exactly results mean. If you feel that something is unclear or should be added, please let me know.

diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html index 1f6efd6579..700fe1b883 100644 --- a/docs/CodingStandards.html +++ b/docs/CodingStandards.html @@ -93,7 +93,7 @@ Every source file should have a header on it that describes the basic purpose of //===----------------------------------------------------------------------===// -A few things to note about this particular format. The "-*- C++ -*-" string on the first line is there to tell Emacs that the source file is a C++ file, not a C file (Emacs assumes .h files are C files by default [Note that tag this is not neccesary in .cpp files]). The name of the file is also on the first line, along with a very short description of the purpose of the file. This is important when printing out code and flipping though lots of pages.

+A few things to note about this particular format. The "-*- C++ -*-" string on the first line is there to tell Emacs that the source file is a C++ file, not a C file (Emacs assumes .h files are C files by default [Note that tag this is not necessary in .cpp files]). The name of the file is also on the first line, along with a very short description of the purpose of the file. This is important when printing out code and flipping though lots of pages.

The main body of the description does not have to be very long in most cases. Here it's only two lines. If an algorithm is being implemented or something tricky is going on, a reference to the paper where it is published should be included, as well as any notes or "gotchas" in the code to watch out for.

@@ -105,7 +105,7 @@ Classes are one fundemental part of a good object oriented design. As such, a c

  • Method information

    • -Methods defined in a class (as well as any global functions) should also be documented properly. A quick note about what it does any a description of the borderline behaviour is all that is neccesary here (unless something particularly tricky or insideous is going on). The hope is that people can figure out how to use your interfaces without reading the code itself... that is the goal metric.

    +Methods defined in a class (as well as any global functions) should also be documented properly. A quick note about what it does any a description of the borderline behaviour is all that is necessary here (unless something particularly tricky or insideous is going on). The hope is that people can figure out how to use your interfaces without reading the code itself... that is the goal metric.

    Good things to talk about here are what happens when something unexpected happens: does the method return null? Abort? Format your hard disk?

    diff --git a/docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt b/docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt index 4d2879554a..5c87330fb7 100644 --- a/docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt +++ b/docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt @@ -150,7 +150,7 @@ needed... 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 diff --git a/docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt b/docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt index 2e0b794075..b546301d35 100644 --- a/docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt +++ b/docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt @@ -144,7 +144,7 @@ least*: 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: diff --git a/docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt b/docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt index 9709ce5db5..2ca46117ca 100644 --- a/docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt +++ b/docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt @@ -43,7 +43,7 @@ Changes: 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: diff --git a/docs/OpenProjects.html b/docs/OpenProjects.html index 740c9db103..574f4d34d3 100644 --- a/docs/OpenProjects.html +++ b/docs/OpenProjects.html @@ -92,7 +92,7 @@ could use the following improvements:

  • Graphs - It would be great to have gnuplot graphs to keep track of how the tree is changing over time. We already gather a several statistics, it - just neccesary to add the script-fu to gnuplotize it. + just necessary to add the script-fu to gnuplotize it.
  • Regression tests - We should run the regression tests in addition to the program tests... diff --git a/docs/ProgrammersManual.html b/docs/ProgrammersManual.html index 6c2659876b..be40ba32f1 100644 --- a/docs/ProgrammersManual.html +++ b/docs/ProgrammersManual.html @@ -1452,7 +1452,7 @@ list.

  • Function::BasicBlockListType &getBasicBlockList()

    Returns the list of BasicBlocks. This is -neccesary to use when you need to update the list or perform a complex action +necessary to use when you need to update the list or perform a complex action that doesn't have a forwarding method.

    @@ -1467,7 +1467,7 @@ These are forwarding methods that make it easy to access the contents of a

  • Function::ArgumentListType &getArgumentList()

    Returns the list of Arguments. This is -neccesary to use when you need to update the list or perform a complex action +necessary to use when you need to update the list or perform a complex action that doesn't have a forwarding method.

    @@ -1583,7 +1583,7 @@ list.

  • Module::FunctionListType &getFunctionList()

    Returns the list of Functions. This is -neccesary to use when you need to update the list or perform a complex action +necessary to use when you need to update the list or perform a complex action that doesn't have a forwarding method.

    @@ -1601,7 +1601,7 @@ list.

  • Module::GlobalListType &getGlobalList()

    Returns the list of GlobalVariables. -This is neccesary to use when you need to update the list or perform a complex +This is necessary to use when you need to update the list or perform a complex action that doesn't have a forwarding method.

    diff --git a/docs/WritingAnLLVMPass.html b/docs/WritingAnLLVMPass.html index a39369fc29..e176435a15 100644 --- a/docs/WritingAnLLVMPass.html +++ b/docs/WritingAnLLVMPass.html @@ -367,7 +367,7 @@ available, from the most general to the most specific.

    When choosing a superclass for your Pass, you should choose the most specific class possible, while still being able to meet the requirements -listed. This gives the LLVM Pass Infrastructure information neccesary to +listed. This gives the LLVM Pass Infrastructure information necessary to optimize how passes are run, so that the resultant compiler isn't unneccesarily slow.

    @@ -476,7 +476,7 @@ href="http://llvm.cs.uiuc.edu/doxygen/LowerAllocations_8cpp-source.html">LowerAl pass. This pass converts malloc and free instructions into platform dependant malloc() and free() function calls. It uses the doInitialization method to get a reference to the malloc and -free functions that it needs, adding prototypes to the module if neccesary.

    +free functions that it needs, adding prototypes to the module if necessary.

    The runOnFunction method