Merged in release_15.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@22120 91177308-0d34-0410-b5e6-96231b3b80d8

4 files changed, 21 insertions, 21 deletions

diff --git a/docs/CFEBuildInstrs.html b/docs/CFEBuildInstrs.html
index ffec8105048..5237ae698c1 100644
--- a/docs/CFEBuildInstrs.html
+++ b/docs/CFEBuildInstrs.html
@@ -129,7 +129,7 @@ of permissions. Specify a path into which LLVM can be installed (e.g.
 </pre></li>
 
 <li><p>Unpack the C/C++ front-end source into cfrontend/src, either by
-       untar'ing an llvm-gcc.tar.gz file or checking out CVS into this
+       untar'ing a cfrontend.source.tar.gz file or checking out CVS into this
        directory.</p></li>
 
 <li><p>Make "build" and "install" directories as siblings of the "src" tree:</p>
diff --git a/docs/CommandGuide/Makefile b/docs/CommandGuide/Makefile
index 54f4cef1e13..d25f4cbee4d 100644
--- a/docs/CommandGuide/Makefile
+++ b/docs/CommandGuide/Makefile
@@ -30,7 +30,7 @@ html/%.html: %.pod
 	  --podpath=. --noindex --infile=$< --outfile=$@ --title=$*
 
 man/man1/%.1: %.pod
-	pod2man --release=1.4 --center="LLVM Command Guide" $< $@
+	pod2man --release=1.5 --center="LLVM Command Guide" $< $@
 
 ps/%.ps: man/man1/%.1
 	groff -Tps -man $< > $@
diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html
index 3831b4d36aa..0ad6fa06b12 100644
--- a/docs/GettingStarted.html
+++ b/docs/GettingStarted.html
@@ -307,9 +307,9 @@ if necessary.</li>
 </div>
 
 <p>Note that you will need about 1-3 GB of space for a full LLVM build in Debug
-mode, depending on the system (because of all the debug info), and the libraries
-appear in more than one of the tools that get linked, so there is some
-duplication.  If you do not need many of the tools and you are space-conscious,
+mode, depending on the system (it is so large because of all the debugging
+information and the fact that the libraries are statically linked into multiple
+tools).  If you do not need many of the tools and you are space-conscious,
 you can disable them individually in <tt>llvm/tools/Makefile</tt>.  The Release
 build requires considerably less space.</p>
 
@@ -576,9 +576,10 @@ variables.
 <dl>
   <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bytecode/libs</tt></dt>
   <dd>[Optional] This environment variable helps LLVM linking tools find the
-  locations of your bytecode libraries. It is provided only a
+  locations of your bytecode libraries. It is provided only as a
   convenience since you can specify the paths using the -L options of the
-  tools and the C/C++ front-end will use the bytecode files installed in its
+  tools and the C/C++ front-end will automatically use the bytecode files
+  installed in its
   <tt>lib</tt> directory.</dd>
 </dl>
 
@@ -620,7 +621,7 @@ compressed with the gzip program.
   <dt><tt>cfrontend-x.y.i386-unknown-freebsd5.1.tar.gz</tt></dt>
   <dd>Binary release of the GCC front end for FreeBSD/x86.<br/></dd>
 
-  <dt><tt>cfrontend-x.y.powerpc-apple-darwin7.6.0.tar.gz</tt></dt>
+  <dt><tt>cfrontend-x.y.powerpc-apple-darwin7.8.0.tar.gz</tt></dt>
   <dd>Binary release of the GCC front end for MacOS X/PPC.<br/></dd>
 </dl>
 
@@ -788,11 +789,12 @@ script to configure the build system:</p>
   <a href="CFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
   for details on building the C/C++ Front End.</dd>
   <dt><i>--with-tclinclude</i></dt>
-  <dd>Path to the tcl include directory under which the <tt>tclsh</tt> can be
+  <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
   found. Use this if you have multiple tcl installations on your machine and you
   want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
   dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
-  option, the LLVM configure script will search for tcl 8.4 and 8.3 releases.
+  option, the LLVM configure script will search for the tcl 8.4 and 8.3
+  releases.
   <p></p>
   </dd>
   <dt><i>--enable-optimized</i></dt>
@@ -817,7 +819,7 @@ script to configure the build system:</p>
   native compiler (no cross-compiler targets available). The "native" target is 
   selected as the target of the build host. You can also specify a comma 
   separated list of target names that you want available in llc. The target 
-  names use all lower case. The current set is of targets is: <br/>
+  names use all lower case. The current set of targets is: <br/>
   <tt>alpha, ia64, powerpc, skeleton, sparc, x86</tt>.
   <p></p></dd>
   <dt><i>--enable-doxygen</i></dt>
@@ -1148,7 +1150,7 @@ different <a href="#tools">tools</a>.</p>
   <dd> This directory contains files that describe various target architectures
   for code generation.  For example, the <tt>llvm/lib/Target/SparcV9</tt> 
   directory holds the Sparc machine description while
-  <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter</dd>
+  <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
     
   <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
   <dd> This directory contains the major parts of the code generator: Instruction 
@@ -1251,8 +1253,8 @@ information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
   all from one command line. <tt>llvmc</tt> also takes care of processing the
   dependent libraries found in bytecode. This reduces the need to get the
   traditional <tt>-l&lt;name&gt;</tt> options right on the command line. Please
-  note that this tool is new in 1.4 and considered experimental. It will be
-  fully supported in 1.5.</dd>
+  note that this tool, while functional, is still experimental and not feature
+  complete.</dd>
 
   <dt><tt><b>llvm-ar</b></tt></dt>
   <dd>The archiver produces an archive containing
@@ -1271,9 +1273,8 @@ information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
   <dd><tt>llvm-ld</tt> is very similar to gccld and provides a general purpose
   and extensible linker for LLVM. This is the linker invoked by <tt>llvmc</tt>.
   It allows optimization modules to be loaded so that language specific
-  optimizations can be applied at link time. Please note that this tool is new
-  in LLVM 1.4 and still considered experimental. It will be fully supported in
-  LLVM 1.5.</dd>
+  optimizations can be applied at link time. This tool is considered
+  experimental.</dd>
 
   <dt><tt><b>llvm-link</b></tt></dt>
   <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into 
@@ -1291,7 +1292,7 @@ information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
 
   <dt><tt><b>llc</b></tt></dt>
   <dd> <tt>llc</tt> is the LLVM backend compiler, which
-  translates LLVM bytecode to a SPARC or x86 assembly file, or to C code (with
+  translates LLVM bytecode to a native code assembly file or to C code (with
   the -march=c option).</dd>
 
   <dt><tt><b>llvm-gcc</b></tt></dt>
@@ -1299,8 +1300,7 @@ information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
   that has been retargeted to emit LLVM code as the machine code output.  It
   works just like any other GCC compiler, taking the typical <tt>-c, -S, -E,
   -o</tt> options that are typically used.  The source code for the
-  <tt>llvm-gcc</tt> tool is currently not included in the LLVM CVS tree
-  because it is quite large and not very interesting.
+  <tt>llvm-gcc</tt> tool is available as a separate CVS module.
   <blockquote>
     <dl>
       <dt><tt><b>gccas</b></tt></dt>
diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html
index fb0c7fbfbd5..1c2db4eb0c7 100644
--- a/docs/ReleaseNotes.html
+++ b/docs/ReleaseNotes.html
@@ -694,7 +694,7 @@ frontends.</li>
 <div class="doc_text">
 
 <ul>
-  <li>None yet</li>
+<li><a href="http://llvm.cs.uiuc.edu/PR566">Memory Mapped I/O Intrinsics do not fence memory</a></li>
 </ul>
 
 </div>