From: Sean Silva Date: Mon, 7 Apr 2014 22:29:53 +0000 (+0000) Subject: [docs] Fix some Sphinx warnings that have crept in. X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=71e245c1f6047e4e66340fd744fdbe1284b3058c;p=oota-llvm.git [docs] Fix some Sphinx warnings that have crept in. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@205742 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/CMake.rst b/docs/CMake.rst index cbca1dbeb57..3049ac0f2ac 100644 --- a/docs/CMake.rst +++ b/docs/CMake.rst @@ -306,14 +306,13 @@ LLVM-specific variables **LLVM_DOXYGEN_QHP_NAMESPACE**:STRING Namespace under which the intermediate Qt Help Project file lives. See `Qt - Help Project `_ + Help Project`_ for more information. Defaults to "org.llvm". This option is only useful in combination with ``-DLLVM_ENABLE_DOXYGEN_QT_HELP=ON``; otherwise this has no effect. **LLVM_DOXYGEN_QHP_CUST_FILTER_NAME**:STRING - See `Qt Help Project - `_ for + See `Qt Help Project`_ for more information. Defaults to the CMake variable ``${PACKAGE_STRING}`` which is a combination of the package name and version string. This filter can then be used in Qt Creator to select only documentation from LLVM when browsing @@ -321,6 +320,8 @@ LLVM-specific variables useful in combination with ``-DLLVM_ENABLE_DOXYGEN_QT_HELP=ON``; otherwise this has no effect. +.. _Qt Help Project: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-filters + **LLVM_DOXYGEN_QHELPGENERATOR_PATH**:STRING The path to the ``qhelpgenerator`` executable. Defaults to whatever CMake's ``find_program()`` can find. This option is only useful in combination with diff --git a/docs/LangRef.rst b/docs/LangRef.rst index 91692ad41ed..0654ca62e3d 100644 --- a/docs/LangRef.rst +++ b/docs/LangRef.rst @@ -6968,7 +6968,7 @@ cache (e.g. ARM, MIPS), the intrinsic is lowered either to appropiate instructions or a system call, if cache flushing requires special privileges. -The default behavior is to emit a call to ``__clear_cache'' from the run +The default behavior is to emit a call to ``__clear_cache`` from the run time library. This instrinsic does *not* empty the instruction pipeline. Modifications