use https for llvm.org in the doc

llvm-svn: 370303

diff --git a/lldb/docs/index.rst b/lldb/docs/index.rst
index da7a12e6e28f7c911c69c0d29687c4fe951dd799..7e287b1d9ae4b3e7a4833231deca68d2766f4d4b 100644 (file)
--- a/lldb/docs/index.rst
+++ b/lldb/docs/index.rst
@@ -15,7 +15,7 @@ Objective-C and C++ on the desktop and iOS devices and simulator.
 All of the code in the LLDB project is available under the
 `"Apache 2.0 License with LLVM exceptions"`_.
 
-.. _"Apache 2.0 License with LLVM exceptions": http://llvm.org/docs/DeveloperPolicy.html#new-llvm-project-license-framework
+.. _"Apache 2.0 License with LLVM exceptions": https://llvm.org/docs/DeveloperPolicy.html#new-llvm-project-license-framework
 
 Why a New Debugger?
 -------------------
@@ -159,6 +159,6 @@ interesting areas to contribute to lldb.
    :maxdepth: 1
    :caption: External Links
 
-   Source Code <http://llvm.org/viewvc/llvm-project/lldb/trunk/>
+   Source Code <https://llvm.org/viewvc/llvm-project/lldb/trunk/>
    Code Reviews <https://reviews.llvm.org>
    Bug Reports <https://bugs.llvm.org/>

diff --git a/lldb/docs/resources/build.rst b/lldb/docs/resources/build.rst
index 71ce5a6afc4cd1d8b20fa3e7514d2949dadcc59a..62981e0f233449fe54d47e01722bb2d020d14787 100644 (file)
--- a/lldb/docs/resources/build.rst
+++ b/lldb/docs/resources/build.rst
@@ -12,7 +12,7 @@ In particular, it requires both Clang and LLVM itself in order to build. Due to
 this tight integration the Getting Started guides for both of these projects
 come as prerequisite reading:
 
-* `LLVM <http://llvm.org/docs/GettingStarted.html>`_
+* `LLVM <https://llvm.org/docs/GettingStarted.html>`_
 * `Clang <http://clang.llvm.org/get_started.html>`_
 
 The following requirements are shared on all platforms.
@@ -93,7 +93,7 @@ CMake is a cross-platform build-generator tool. CMake does not build the
 project, it generates the files needed by your build tool. The recommended
 build tool for LLVM is Ninja, but other generators like Xcode or Visual Studio
 may be used as well. Please also read `Building LLVM with CMake
-<http://llvm.org/docs/CMake.html>`_.
+<https://llvm.org/docs/CMake.html>`_.
 
 Regular in-tree builds
 **********************
@@ -278,7 +278,7 @@ CMake caches
 
 CMake caches allow to store common sets of configuration options in the form of
 CMake scripts and can be useful to reproduce builds for particular use-cases
-(see by analogy `usage in LLVM and Clang <http://llvm.org/docs/AdvancedBuilds.html>`_).
+(see by analogy `usage in LLVM and Clang <https://llvm.org/docs/AdvancedBuilds.html>`_).
 A cache is passed to CMake with the ``-C`` flag, following the absolute path to
 the file on disk. Subsequent ``-D`` options are still allowed. Please find the
 currently available caches in the `lldb/cmake/caches/
@@ -290,7 +290,7 @@ Common configurations on macOS
 
 Build, test and install a distribution of LLDB from the `monorepo
 <https://github.com/llvm/llvm-project>`_ (see also `Building a Distribution of
-LLVM <http://llvm.org/docs/BuildingADistribution.html>`_):
+LLVM <https://llvm.org/docs/BuildingADistribution.html>`_):
 
 ::
 

diff --git a/lldb/docs/resources/source.rst b/lldb/docs/resources/source.rst
index 90f94237232b91b8804bf012d4d0228097012f55..0216d30d5c061e13b2337642dc095e36bc9f572b 100644 (file)
--- a/lldb/docs/resources/source.rst
+++ b/lldb/docs/resources/source.rst
@@ -2,7 +2,7 @@ Getting the Sources
 ===================
 
 Refer to the `LLVM Getting Started Guide
-<http://llvm.org/docs/GettingStarted.html#getting-started-with-llvm>`_
+<https://llvm.org/docs/GettingStarted.html#getting-started-with-llvm>`_
 for general instructions on how to check out source. Note that LLDB
 depends on having a working checkout of LLVM and Clang, so the first
 step is to download and build as described at the above URL. The same
@@ -17,7 +17,7 @@ Contributing to LLDB
 --------------------
 
 Please refer to the `LLVM Developer Policy
-<http://llvm.org/docs/DeveloperPolicy.html>`_ for information about
+<https://llvm.org/docs/DeveloperPolicy.html>`_ for information about
 authoring and uploading a patch. LLDB differs from the LLVM Developer
 Policy in the following respects.
 
@@ -40,9 +40,9 @@ rules of thumb:
 * Invalid input.  To deal with invalid input, such as malformed DWARF,
   missing object files, or otherwise inconsistent debug info, LLVM's
   error handling types such as `llvm::Expected<T>
-  <http://llvm.org/doxygen/classllvm_1_1Expected.html>`_ or
+  <https://llvm.org/doxygen/classllvm_1_1Expected.html>`_ or
   `llvm::Optional<T>
-  <http://llvm.org/doxygen/classllvm_1_1Optional.html>`_ should be
+  <https://llvm.org/doxygen/classllvm_1_1Optional.html>`_ should be
   used. Functions that may fail should return their result using these
   wrapper types instead of using a bool to indicate success. Returning
   a default value when an error occurred is also discouraged.
@@ -74,7 +74,7 @@ rules of thumb:
 * Fatal errors.  Aborting LLDB's process using
   `llvm::report_fatal_error()` or `abort()` should be avoided at all
   costs.  It's acceptable to use `llvm_unreachable()
-  <http://llvm.org/doxygen/Support_2ErrorHandling_8h.html>`_ for
+  <https://llvm.org/doxygen/Support_2ErrorHandling_8h.html>`_ for
   actually unreachable code such as the default in an otherwise
   exhaustive switch statement.