[PassManager] Tuning Memory Usage of AnalysisUsage

[oota-llvm.git] / docs / index.rst

diff --git a/docs/index.rst b/docs/index.rst
index 2cc5b8bf095780ee34a9897133451f806010067f..a69ecfedc580789da8916982a7894bb74477c7c8 100644 (file)
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -86,6 +86,7 @@ representation.
    GetElementPtr
    Frontend/PerformanceTips
    MCJITDesignAndImplementation
+   CompileCudaWithLLVM
 
 :doc:`GettingStarted`
    Discusses how to get up and running quickly with the LLVM infrastructure.
@@ -252,7 +253,7 @@ For API clients and LLVM developers.
    WritingAnLLVMPass
    HowToUseAttributes
    NVPTXUsage
-   R600Usage
+   AMDGPUUsage
    StackMaps
    InAlloca
    BigEndianNEON
@@ -260,6 +261,8 @@ For API clients and LLVM developers.
    Statepoints
    MergeFunctions
    BitSets
+   FaultMaps
+   MIRLangRef
 
 :doc:`WritingAnLLVMPass`
    Information on how to write LLVM transformations and analyses.
@@ -272,6 +275,10 @@ For API clients and LLVM developers.
    working on retargetting LLVM to a new architecture, designing a new codegen
    pass, or enhancing existing components.
 
+:doc:`Machine IR (MIR) Format Reference Manual <MIRLangRef>`
+   A reference manual for the MIR serialization format, which is used to test
+   LLVM's code generation passes.
+
 :doc:`TableGen <TableGen/index>`
    Describes the TableGen tool, which is used heavily by the LLVM code
    generator.
@@ -338,8 +345,8 @@ For API clients and LLVM developers.
 :doc:`NVPTXUsage`
    This document describes using the NVPTX back-end to compile GPU kernels.
 
-:doc:`R600Usage`
-   This document describes how to use the R600 back-end.
+:doc:`AMDGPUUsage`
+   This document describes how to use the AMDGPU back-end.
 
 :doc:`StackMaps`
   LLVM support for mapping instruction addresses to the location of
@@ -362,6 +369,12 @@ For API clients and LLVM developers.
 :doc:`InAlloca`
   Description of the ``inalloca`` argument attribute.
 
+:doc:`FaultMaps`
+  LLVM support for folding control flow into faulting machine instructions.
+
+:doc:`CompileCudaWithLLVM`
+  LLVM support for CUDA.
+
 Development Process Documentation
 =================================
 
@@ -421,12 +434,12 @@ Mailing Lists
 If you can't find what you need in these docs, try consulting the mailing
 lists.
 
-`Developer's List (llvmdev)`__
+`Developer's List (llvm-dev)`__
   This list is for people who want to be included in technical discussions of
   LLVM. People post to this list when they have questions about writing code
   for or using the LLVM tools. It is relatively low volume.
 
-  .. __: http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
+  .. __: http://lists.llvm.org/mailman/listinfo/llvm-dev
 
 `Commits Archive (llvm-commits)`__
   This list contains all commit messages that are made when LLVM developers
@@ -435,26 +448,26 @@ lists.
   stay on the bleeding edge of LLVM development. This list is very high
   volume.
 
-  .. __: http://lists.cs.uiuc.edu/pipermail/llvm-commits/
+  .. __: http://lists.llvm.org/pipermail/llvm-commits/
 
-`Bugs & Patches Archive (llvmbugs)`__
+`Bugs & Patches Archive (llvm-bugs)`__
   This list gets emailed every time a bug is opened and closed. It is
-  higher volume than the LLVMdev list.
+  higher volume than the LLVM-dev list.
 
-  .. __: http://lists.cs.uiuc.edu/pipermail/llvmbugs/
+  .. __: http://lists.llvm.org/pipermail/llvm-bugs/
 
 `Test Results Archive (llvm-testresults)`__
   A message is automatically sent to this list by every active nightly tester
   when it completes.  As such, this list gets email several times each day,
   making it a high volume list.
 
-  .. __: http://lists.cs.uiuc.edu/pipermail/llvm-testresults/
+  .. __: http://lists.llvm.org/pipermail/llvm-testresults/
 
 `LLVM Announcements List (llvm-announce)`__
   This is a low volume list that provides important announcements regarding
   LLVM.  It gets email about once a month.
 
-  .. __: http://lists.cs.uiuc.edu/mailman/listinfo/llvm-announce
+  .. __: http://lists.llvm.org/mailman/listinfo/llvm-announce
 
 IRC
 ---