From 98d0636b137779f2fc55ca9ea84a2b97d5daedc8 Mon Sep 17 00:00:00 2001 From: John Criswell Date: Sun, 21 Nov 2004 14:58:12 +0000 Subject: Corrected spelling mistakes. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@18090 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CompilerDriver.html | 6 +++--- docs/SystemLibrary.html | 16 ++++++++-------- docs/index.html | 2 +- 3 files changed, 12 insertions(+), 12 deletions(-) (limited to 'docs') diff --git a/docs/CompilerDriver.html b/docs/CompilerDriver.html index 0c514e8..5568b20 100644 --- a/docs/CompilerDriver.html +++ b/docs/CompilerDriver.html @@ -176,7 +176,7 @@ program.

The following table shows the inputs, outputs, and command line options - applicabe to each phase.

+ applicable to each phase.

@@ -593,12 +593,12 @@ optimization.

Substitutions
-

On any configruation item that ends in command, you must +

On any configuration item that ends in command, you must specify substitution tokens. Substitution tokens begin and end with a percent sign (%) and are replaced by the corresponding text. Any substitution token may be given on any command line but some are more useful than others. In particular each command should have both an %in% - and an %out% substittution. The table below provides definitions of + and an %out% substitution. The table below provides definitions of each of the allowed substitution tokens.

Phase
diff --git a/docs/SystemLibrary.html b/docs/SystemLibrary.html index 9858cdb..a7e8b05 100644 --- a/docs/SystemLibrary.html +++ b/docs/SystemLibrary.html @@ -24,7 +24,7 @@
  • No Exposed Data
  • Throw Only std::string
  • No throw() Specifications
  • -
  • No Duplicate Impementations
  • +
  • No Duplicate Implementations
  • System Library Design
      @@ -40,7 +40,7 @@
    1. System Library Details
      1. Tracking Bugzilla Bug: 351
      2. -
      3. Reference Implementatation
      4. +
      5. Reference Implementation
    2. @@ -85,7 +85,7 @@
      -

      The library must sheild LLVM from all system libraries. To obtain +

      The library must shield LLVM from all system libraries. To obtain system level functionality, LLVM must #include "llvm/System/Thing.h" and nothing else. This means that Thing.h cannot expose any system header files. This protects LLVM from accidentally using system specific @@ -154,7 +154,7 @@

      • foo: Unable to open file because it doesn't exist."

      The "foo:" part is the context. The "Unable to open file" part is the error message. The "because it doesn't exist." part is the reason. This message has - no suggestion. Where possible, the imlementation of lib/System should use + no suggestion. Where possible, the implementation of lib/System should use operating system specific facilities for converting the error code returned by a system call into an error message. This will help to make the error message more familiar to users of that type of operating system.

      @@ -171,7 +171,7 @@

      None of the lib/System interface functions may be declared with C++ throw() specifications on them. This requirement makes sure that the - compler does not insert addtional exception handling code into the interface + compiler does not insert additional exception handling code into the interface functions. This is a performance consideration: lib/System functions are at the bottom of the many call chains and as such can be frequently called. We need them to be as efficient as possible.

      @@ -374,7 +374,7 @@ Notes:

      In order to provide different implementations of the lib/System interface for different platforms, it is necessary for the library to "sense" which operating system is being compiled for and conditionally compile only the - applicabe parts of the library. While several operating system wrapper + applicable parts of the library. While several operating system wrapper libraries (e.g. APR, ACE) choose to use #ifdef preprocessor statements in combination with autoconf variable (HAVE_* family), lib/System chooses an alternate strategy.

      @@ -383,7 +383,7 @@ Notes: functions for a particular operating system variant. The functions defined in that file have no #ifdef's to disambiguate the platform since the file is only compiled on one kind of platform. While this leads to the same function being - imlemented differently in different files, it is our contention that this + implemented differently in different files, it is our contention that this leads to better maintenance and easier portability.

      For example, consider a function having different implementations on a variety of platforms. Many wrapper libraries choose to deal with the different @@ -407,7 +407,7 @@ Notes: specific flavors and versions of the operating system. In that case you end up with multiple levels of nested #if statements. This is what we mean by "#ifdef hell".

      -

      To avoid the situation above, we've choosen to locate all functions for a +

      To avoid the situation above, we've chosen to locate all functions for a given implementation file for a specific operating system into one place. This has the following advantages:

        diff --git a/docs/index.html b/docs/index.html index cbd8ceb..c90ab9a 100644 --- a/docs/index.html +++ b/docs/index.html @@ -171,7 +171,7 @@ generator. on how to write a new alias analysis implementation or how to use existing analyses. -
      • The Stacker Cronicles - This document +
      • The Stacker Chronicles - This document describes both the Stacker language and LLVM frontend, but also some details about LLVM useful for those writing front-ends.
      • -- cgit v1.1