[llvm-commits] [llvm] r52106 - /llvm/trunk/docs/ReleaseNotes.html

[Dan Gohman]

Author: djg
Date: Sun Jun  8 17:57:59 2008
New Revision: 52106

URL: http://llvm.org/viewvc/llvm-project?rev=52106&view=rev
Log:
Add some links to doxygen documentation.

Modified:
    llvm/trunk/docs/ReleaseNotes.html

Modified: llvm/trunk/docs/ReleaseNotes.html
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/ReleaseNotes.html?rev=52106&r1=52105&r2=52106&view=diff

==============================================================================
--- llvm/trunk/docs/ReleaseNotes.html (original)
+++ llvm/trunk/docs/ReleaseNotes.html Sun Jun  8 17:57:59 2008
@@ -101,9 +101,14 @@
     standardize on <tt>FOOCLASS::Create</tt> for all IR classes in the future,
     but not all of them have been moved over yet.</li>
 <li>LLVM 2.3 renames the LLVMBuilder and LLVMFoldingBuilder classes to
-   IRBuilder.</li>
-<li>MRegisterInfo was renamed to TargetRegisterInfo.</li>
-<li>The MappedFile class is gone, please use MemoryBuffer instead.</li>
+    <a href="http://llvm.org/doxygen/classllvm_1_1IRBuilder.html">IRBuilder</a>.
+    </li>
+<li>MRegisterInfo was renamed to
+    <a href="http://llvm.org/doxygen/classllvm_1_1TargetRegisterInfo.html">
+    TargetRegisterInfo</a>.</li>
+<li>The MappedFile class is gone, please use
+    <a href="http://llvm.org/doxygen/classllvm_1_1MemoryBuffer.html">
+    MemoryBuffer</a> instead.</li>
 <li>The '<tt>-enable-eh</tt>' flag to llc has been removed.  Now code should 
     encode whether it is safe to omit unwind information for a function by
     tagging the Function object with the '<tt>nounwind</tt>' attribute.</li>
@@ -372,7 +377,8 @@
     both pre-pass and post-pass scheduling, and to improve compiler-debugging
     output.</li>
 
-<li>The target-independent code generator infrastructure now uses LLVM's APInt
+<li>The target-independent code generator infrastructure now uses LLVM's
+    <a href="http://llvm.org/doxygen/classllvm_1_1APInt.html">APInt</a>
     class to handle integer values, which allows it to support integer types
     larger than 64 bits. Note that support for such types is also dependent on
     target-specific support. Use of APInt is also a step toward support for